Example.com is a specialized domain name reserved by the Internet Assigned Numbers Authority (IANA) for use in documentation, manuals, and technical examples. Established through official Internet Engineering Task Force (IETF) standards, it provides a safe, non-routable destination for developers and writers to illustrate web concepts without risking interference with live websites.
The landscape of the internet in 2026 continues to rely heavily on standardized placeholders. While millions of new domains are registered every year, example.com, along with its siblings example.net, example.org, and example.edu, remains the gold standard for technical clarity. These domains are not available for registration by the public; they are permanently held by ICANN (Internet Corporation for Assigned Names and Numbers) to ensure they serve as a universal utility for the global technical community.
The Origin and Purpose of Reserved Domain Names
The necessity for reserved domains arose during the rapid expansion of the internet in the late 1990s. Before standardized placeholders existed, technical writers and software developers often used real domains—or invented ones—to demonstrate how software, networks, or URLs functioned. This practice created several significant problems:
- Unintended Traffic: If a tutorial used
test.comas an example, the owner oftest.comwould receive massive amounts of unwanted "garbage" traffic from users following the tutorial. - Security Risks: Using a real domain in an example could lead users to visit a site that might later be purchased by a malicious actor (typosquatting).
- Broken Examples: If a writer used a domain that eventually expired or changed hands, the example would become confusing or irrelevant.
To solve these issues, the IETF published RFC 2606 in June 1999. This document officially reserved several domain names and top-level domains (TLDs) for documentation purposes. The core idea was to provide a set of labels that everyone would recognize as "not real," yet would still follow the syntactical rules of the Domain Name System (DNS).
The Evolution of Special-Use Domain Names
As the internet evolved, the management of these names became more formal. In 2013, the IETF published RFC 6761, which expanded the definition of "Special-Use Domain Names." This document outlined exactly how software, DNS servers, and network operators should handle reserved names like example.com.
According to these standards, software should generally recognize these names as special and avoid trying to resolve them in ways that would impact the global DNS root. For instance, a web browser or a local network configuration should ideally treat these domains as placeholders that do not require external lookup, although in practice, example.com does resolve to a specific IP address managed by IANA to provide a standard landing page.
The Role of IANA and ICANN in Managing Example.com
The management of example.com falls under the jurisdiction of the Internet Assigned Numbers Authority (IANA), which is a function of the Internet Corporation for Assigned Names and Numbers (ICANN). These organizations ensure that the domain remains stable and functional for its intended purpose.
When you navigate to example.com in your browser today, you are greeted by a simple, clean page. This page explicitly states that the domain is established for use in illustrative examples in documents and is not available for purchase. This landing page is crucial because it confirms to a user or developer that their connection is working correctly, even if the "destination" is merely a placeholder.
Technical Infrastructure of the Reserved Domains
While example.com appears simple, its back-end management is handled with the same level of security as the DNS root zone. ICANN maintains the DNS records for these domains, including:
- A Records (IPv4): Currently pointing to 93.184.215.14.
- AAAA Records (IPv6): Ensuring the domain works in modern networking environments.
- DNSSEC: The domains are signed with DNS Security Extensions to prevent spoofing, ensuring that when a developer uses them for testing, the results are predictable and secure.
Why You Should Use Example.com Instead of Custom Placeholders
In professional software development and technical writing, the use of example.com is considered a best practice for several reasons. Avoiding "fake" domains like yourname.com or mysite.test (unless specifically testing TLD behavior) prevents technical debt and security vulnerabilities.
Preventing "Leaked" Data and Traffic
When developers use real-sounding domains in their codebases—such as api.internal-test.com—there is a risk that this configuration might accidentally be pushed to a production environment. If the domain internal-test.com is actually owned by a third party, sensitive data (like API keys or user tokens) could be sent to an external server. By using example.com, any leaked data is sent to a known, non-malicious sinkhole managed by ICANN, or it simply fails to resolve depending on the network configuration.
Universal Recognition and Accessibility
Standardization is the bedrock of the internet. When a developer in Tokyo reads a tutorial written by a developer in London, the use of example.com provides immediate context. It signals: "This is a placeholder; replace this with your own domain." If the writer used a localized or creative domain name, the reader might waste time wondering if that specific domain is a prerequisite for the software being discussed.
Consistency Across Documentation
For organizations that manage large quantities of internal and external documentation, using a standardized reserved domain ensures that all examples remain consistent. It allows automated tools to easily identify where placeholders are used, making it simpler to run scripts that might "find and replace" variables for customized user deployments.
Varieties of Reserved Domains and TLDs
While example.com is the most famous, several other names are reserved under the same standards to provide variety and specific utility. These are categorized into second-level domains and top-level domains (TLDs).
Reserved Second-Level Domains
These are the most commonly used placeholders in web development and documentation.
| Domain | Intended Use Case |
|---|---|
| example.com | The primary placeholder for general web addresses and URLs. |
| example.net | Often used in examples involving network infrastructure or service providers. |
| example.org | Typically used for examples involving non-profits or community organizations. |
| example.edu | Specifically reserved for educational contexts and university-related examples. |
Reserved Top-Level Domains (TLDs)
RFC 2606 also reserved four specific TLDs that are guaranteed never to be sold as part of the global DNS expansion (the program that brought us .app, .blog, etc.).
- .test: Reserved for use in testing new DNS code or localized software.
- .example: Reserved for use in documentation where a TLD itself needs to be a placeholder.
- .invalid: Specifically intended for use in cases where a domain name is clearly intended to be invalid or non-functional.
- .localhost: Reserved to prevent conflict with the local loopback address on a computer.
Practical Use Cases in Software Development
In 2026, the use of example.com has expanded into more complex technological spheres, including API design, cloud orchestration, and automated testing frameworks.
API Documentation and Mocking
When designing a REST or GraphQL API, developers use example.com in their documentation to show the structure of an endpoint. For instance:
GET https://api.example.com/v1/users
This tells the consumer of the API exactly what the URL structure looks like without providing a live endpoint that might be subject to rate limiting or authentication hurdles during the reading phase.
Configuration File Templates
In tools like Kubernetes, Terraform, or Docker, configuration files often require domain names for ingress rules or environment variables. Using example.com in the boilerplate code ensures that if a user accidentally runs the configuration without editing it, the system tries to connect to a safe, neutral domain rather than a sensitive internal resource.
Email System Testing
Testing email flows (registration, password resets, etc.) often requires dummy email addresses. Using user@example.com is the standard approach. This prevents the accidental sending of test emails to real people. Most mail transfer agents (MTAs) are configured to recognize example.com and can be set to discard these messages immediately, preventing them from ever leaving the local network.
Security and Privacy Benefits of Using Reserved Domains
The security implications of domain selection are often overlooked. By adhering to the example.com standard, organizations protect themselves from a variety of "leaky" data scenarios.
Mitigating Typosquatting and Domain Hijacking
In the past, many tutorials used test.com or mysite.com. Over time, these domains were purchased by individuals who realized they could capture significant traffic from people following old tutorials. These "parked" domains often contain aggressive advertising or malware. Because example.com can never be sold or hijacked, it remains a "clean" environment forever. This makes it the only safe choice for long-lived documentation.
Privacy for Developers
When developers are troubleshooting code on forums like Stack Overflow, they often need to share snippets of their configuration. If they use their real corporate domain, they might inadvertently reveal their company's internal naming conventions or infrastructure details. Replacing the sensitive domain with example.com allows the developer to get help while maintaining corporate privacy.
Common Misconceptions and Troubleshooting
Despite its ubiquity, there are still several misconceptions regarding how example.com works and how it should be used.
"Can I buy a subdomain of example.com?"
A common question among new developers is whether they can purchase myname.example.com. The answer is a definitive no. The entire example.com zone is managed by IANA/ICANN. No subdomains are sold or leased to the public.
"Why does example.com actually load a page?"
Some people expect example.com to be a dead link. However, it is a functional domain. IANA maintains a web server for it to provide information about why the domain exists. This is actually a feature, not a bug; it allows network administrators to verify that their DNS resolution and internet connectivity are working using a known-safe destination.
"Does using example.com slow down my tests?"
If your automated tests are attempting to "ping" or "fetch" example.com, they will incur the latency of a real DNS lookup and HTTP request. In high-performance testing environments, it is recommended to "mock" these calls so that they resolve instantly to a local address (like 127.0.0.1) rather than actually hitting the IANA servers. This respects the IANA infrastructure and speeds up your development cycle.
Comparison of Reserved Names for Documentation
To ensure you are using the correct placeholder for your specific needs, consult the following comparison of the most common reserved entities.
| Entity | Category | Best Use Case | Resolves Globally? |
|---|---|---|---|
| example.com | Domain | General documentation, URLs in tutorials. | Yes |
| example.org | Domain | Non-profit or open-source project examples. | Yes |
| .test | TLD | Local software testing, DNS configuration experiments. | No |
| .localhost | TLD | Referencing the local machine's loopback address. | No |
| .invalid | TLD | Proving that a system handles malformed/dead links correctly. | No |
| 192.0.2.0/24 | IP Block | Documentation requiring an IPv4 address (TEST-NET-1). | No |
Summary and Next Actions
The domain example.com is more than just a placeholder; it is a vital piece of the internet's educational and technical infrastructure. By using it, you contribute to a more secure, standardized, and professional web ecosystem. Whether you are writing a simple blog post or architecting a massive cloud system, always reach for the reserved standards first.
Key Recommendations:
- Audit your documentation: Ensure that no real domains (like
google.comoryourcompany.com) are used as placeholders in your manuals or tutorials. - Update code boilerplates: Replace generic names like
testserver.comwithexample.comto prevent accidental data leaks. - Educate your team: Ensure that junior developers and technical writers understand the purpose of RFC 2606 and the security benefits of using reserved domains.
- Use specific TLDs for testing: If you are testing DNS behaviors, use
.testrather than.comto ensure your experiments stay within your local environment.
Frequently Asked Questions
Who owns example.com?
Example.com is owned and managed by the Internet Corporation for Assigned Names and Numbers (ICANN). It is specifically reserved for documentation and is not available for private ownership or registration.
Is it legal to use example.com in my book or website?
Yes, it is not only legal but highly encouraged. The IETF and IANA specifically created these domains so that authors and creators could use them without seeking permission. Using these domains ensures you are following international technical standards.
What happens if I send an email to info@example.com?
Generally, the email will fail to deliver. While the domain has a web server, ICANN typically does not maintain active Mail Exchange (MX) records that accept incoming mail for the domain. Most mail servers will return a "User Unknown" or "Host Unreachable" error.
Can I use example.com in my software’s unit tests?
While you can use it, it is better to "mock" the domain in your testing environment. This means telling your test suite to treat example.com as if it points to your local machine. This prevents your tests from relying on an active internet connection and avoids putting unnecessary load on ICANN's servers.
Are there other domains like example.com for different languages?
The RFCs specifically reserve the English word "example." While some internationalized domain name (IDN) efforts have discussed reserved names in other scripts, example.com remains the globally recognized standard for all technical documentation, regardless of the language of the text.
Is there a limit to how many times I can use example.com?
There is no limit. You can use it as often as necessary in your code, documentation, and presentations. It is a free resource provided to the global community to help make the internet more understandable and secure.
