Reserved Domains as Guaranteed-Stable Documentation Infrastructure

·https://example.com
articleinfrastructureinternetdnsdocumentationstandards

stable-by-design identifiers map directly to how the joelclaw system treats canonical event names and skill slugs — reserved, collision-free, guaranteed

example.com is one of a handful of domains that IANA (Internet Assigned Numbers Authority) permanently reserves under RFC 2606 for documentation, tutorials, and examples. It can’t be bought, sold, squatted, or hijacked. It will never serve ads. It will never expire. It simply exists as a controlled, stable reference point that anyone writing a tutorial, RFC, or code example can use without worrying about breaking someone else’s production DNS.

The full reserved set — example.com, example.net, example.org, example.edu, and the TLD .example itself — are controlled vocabulary for the internet. The idea is simple: if every tutorial used mysite.com or foo.com, some of those would eventually be real domains, creating landmines for anyone copy-pasting code. Reserved domains eliminate that class of problem entirely. Stability by design, not by luck.

The IANA page that resolves at example.com is itself minimal to the point of being almost Zen — a single paragraph explaining that the domain is reserved, with a link to the RFC. No tracking, no redirects, no content that can go stale. It’s the most reliable URL on the internet precisely because there’s nothing there to break.

Key Ideas

  • RFC 2606 (“Reserved Top Level DNS Names”) defines example.com/net/org/edu and the .example, .invalid, .localhost, .test TLDs as permanently reserved for documentation use
  • Controlled vocabulary for identifiers — reserving a namespace rather than hoping for collision avoidance — is a pattern worth applying to any long-lived system
  • IANA maintains the reserved domain list; the full example.* set is covered under their domain registry
  • The .localhost and .test TLDs are similarly reserved and useful for local development without DNS conflicts
  • This “reserved namespace” pattern appears in AT Protocol lexicons (the app.bsky.* namespace hierarchy), in npm’s @scope/* model, and in how the joelclaw system uses prefixed Inngest event names like discovery/noted to avoid collisions

Links

← All discoveries