{
  "@context": "https://schema.org",
  "@id": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-10-01-iana-s-email-about-why-example-com-changed/#webpage",
  "@type": [
    "WebPage",
    "ArchiveComponent"
  ],
  "articleBody": "I emailed IANA (Internet Assigned Numbers Authority) earlier today to ask about the new content on [example.com](https://example.com). To my surprise, their VP replied. Here is the email:\n\n> I am happy to try and answer any questions you have.\n>\n> The changes we make to the site from time-to-time are usually informed by a desire to either reduce the overall bandwidth demands of serving the site, or improve its utility. At its heart it is a placeholder for a site no-one should be accessing, but we have historically showed a message there to inform visitors about why the domain is registered and how they may use it.\n>\n> As it tends to be heavily trafficked, the overall bandwidth is a key consideration, and to that end one of the changes we made this week was to split the page content into a more basic page, augmented by a separate Javascript file with additional content beyond that. Since most of the traffic to the site is automated it tends not to fetch the Javascript file, reducing overall data requirements.\n>\n> The fundamental purpose of the domain is for use in documentation, such as illustrative examples you may find in instructions. We know that people may, for example, cut-and-paste a sample configuration file and forget to customize entries that contain an example domain, and we expect we get some incidental traffic from that. However, the domain isn't intended to be a general purpose endpoint for things like availability testing so we do not encourage that kind of usage. There is no requirement there is a HTTP service present on the host in order to fulfill its purpose, we just operate it as a courtesy.\n>\n> Hope this is helpful. Let us know if you have any questions. You're free to use and recirculate this information as you see fit.\n>\n> Kim Davies\n>\n> Internet Assigned Numbers Authority\n",
  "authors": [
    "oliverdunk.com via videah"
  ],
  "captured_at": "2026-10-01T19:33:44.897168732+00:00",
  "category": "news",
  "content_html": "<p>I emailed IANA (Internet Assigned Numbers Authority) earlier today to ask about the new content on <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://example.com\">example.com</a>. To my surprise, their VP replied. Here is the email:</p>\n<blockquote>\n<p>I am happy to try and answer any questions you have.</p>\n<p>The changes we make to the site from time-to-time are usually informed by a desire to either reduce the overall bandwidth demands of serving the site, or improve its utility. At its heart it is a placeholder for a site no-one should be accessing, but we have historically showed a message there to inform visitors about why the domain is registered and how they may use it.</p>\n<p>As it tends to be heavily trafficked, the overall bandwidth is a key consideration, and to that end one of the changes we made this week was to split the page content into a more basic page, augmented by a separate Javascript file with additional content beyond that. Since most of the traffic to the site is automated it tends not to fetch the Javascript file, reducing overall data requirements.</p>\n<p>The fundamental purpose of the domain is for use in documentation, such as illustrative examples you may find in instructions. We know that people may, for example, cut-and-paste a sample configuration file and forget to customize entries that contain an example domain, and we expect we get some incidental traffic from that. However, the domain isn't intended to be a general purpose endpoint for things like availability testing so we do not encourage that kind of usage. There is no requirement there is a HTTP service present on the host in order to fulfill its purpose, we just operate it as a courtesy.</p>\n<p>Hope this is helpful. Let us know if you have any questions. You're free to use and recirculate this information as you see fit.</p>\n<p>Kim Davies</p>\n<p>Internet Assigned Numbers Authority</p>\n</blockquote>\n",
  "content_markdown": "I emailed IANA (Internet Assigned Numbers Authority) earlier today to ask about the new content on [example.com](https://example.com). To my surprise, their VP replied. Here is the email:\n\n> I am happy to try and answer any questions you have.\n>\n> The changes we make to the site from time-to-time are usually informed by a desire to either reduce the overall bandwidth demands of serving the site, or improve its utility. At its heart it is a placeholder for a site no-one should be accessing, but we have historically showed a message there to inform visitors about why the domain is registered and how they may use it.\n>\n> As it tends to be heavily trafficked, the overall bandwidth is a key consideration, and to that end one of the changes we made this week was to split the page content into a more basic page, augmented by a separate Javascript file with additional content beyond that. Since most of the traffic to the site is automated it tends not to fetch the Javascript file, reducing overall data requirements.\n>\n> The fundamental purpose of the domain is for use in documentation, such as illustrative examples you may find in instructions. We know that people may, for example, cut-and-paste a sample configuration file and forget to customize entries that contain an example domain, and we expect we get some incidental traffic from that. However, the domain isn't intended to be a general purpose endpoint for things like availability testing so we do not encourage that kind of usage. There is no requirement there is a HTTP service present on the host in order to fulfill its purpose, we just operate it as a courtesy.\n>\n> Hope this is helpful. Let us know if you have any questions. You're free to use and recirculate this information as you see fit.\n>\n> Kim Davies\n>\n> Internet Assigned Numbers Authority\n",
  "dateCreated": "2026-10-01T19:33:44.897168732+00:00",
  "date_created": "2026-10-01T08:47:50+00:00",
  "date_modified": "2026-10-01T08:47:50+00:00",
  "date_published": "2026-10-01T08:47:50+00:00",
  "description": "Comments",
  "external_url": "https://www.oliverdunk.com/2026/09/30/iana-reply",
  "git": {
    "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e",
    "path": "items/lobste-rs/2026/10/2026-10-01-iana-s-email-about-why-example-com-changed.md",
    "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/lobste-rs/2026/10/2026-10-01-iana-s-email-about-why-example-com-changed.md"
  },
  "id": "urn:aggr:item:d2071671a2068211b83fc06d761132fb7c40705c",
  "isBasedOn": {
    "@id": "https://www.oliverdunk.com/2026/09/30/iana-reply"
  },
  "mainEntity": {
    "@id": "https://www.oliverdunk.com/2026/09/30/iana-reply",
    "@type": "CreativeWork",
    "archivedAt": {
      "@id": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-10-01-iana-s-email-about-why-example-com-changed/#webpage"
    },
    "author": [
      {
        "@type": "Person",
        "name": "oliverdunk.com via videah"
      }
    ],
    "dateModified": "2026-10-01T08:47:50+00:00",
    "datePublished": "2026-10-01T08:47:50+00:00",
    "headline": "IANA's email about why example.com changed",
    "timeRequired": "PT2M",
    "url": "https://www.oliverdunk.com/2026/09/30/iana-reply",
    "wordCount": 313
  },
  "name": "Archived snapshot: IANA's email about why example.com changed",
  "preview": null,
  "reading_minutes": 2,
  "replicated_at": null,
  "source": "lobste-rs",
  "source_name": "Lobsters: Top Stories of the Past Week",
  "summary": "Comments",
  "tags": [
    "networking",
    "web"
  ],
  "temporalCoverage": "2026-10-01T19:33:44.897168732+00:00",
  "title": "IANA's email about why example.com changed",
  "url": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-10-01-iana-s-email-about-why-example-com-changed/",
  "word_count": 313
}