When you try to register certain domain names, you discover they're simply unavailable, not because someone else owns them, but because they're permanently reserved by technical standards, registry policies, or security requirements. These restrictions exist across multiple levels of the DNS hierarchy, from top-level domains that will never be delegated to second-level names that registries protect, to labels that DNS itself treats specially.
Understanding which names are reserved and why helps you avoid wasting time on registration attempts that will never succeed, explains mysterious DNS behaviors you might encounter, and illuminates the careful design decisions that keep the internet's naming system stable.
IETF Special-Use Domain Names
The Internet Engineering Task Force (IETF) maintains a registry of special-use domain names, TLDs and specific domains that have defined technical purposes and must not be delegated in the global DNS. These reservations prevent conflicts between local network configurations and the public internet.
The .test top-level domain exists exclusively for testing and documentation. You can use example.test, staging.test, or any name under .test in test environments, configuration examples, or documentation without risk of conflicting with real internet domains.
Because .test is reserved and will never be delegated by ICANN, queries for .test domains can safely fail or return locally configured responses without causing confusion. Testing frameworks, development environments, and documentation can use .test domains knowing they won't accidentally reach real internet services.
.localhost and the bare name localhost resolve to the local machine, 127.0.0.1 for IPv4 and ::1 for IPv6. This reservation is hardcoded into operating systems and network stacks, ensuring that localhost always refers to the local system regardless of DNS configuration.
Any name under .localhost (like database.localhost or api.localhost) should also resolve locally, though implementation support varies. The reservation prevents anyone from registering localhost as a real domain that could intercept traffic intended for local services.
.invalid is reserved for names that are explicitly invalid and should never resolve. Documentation might use [email protected] as an example email address that's guaranteed not to work, or test suites might use .invalid domains to verify error handling for unresolvable names. Because .invalid is guaranteed never to resolve, it's safe to use in contexts where you need a syntactically valid domain name that shouldn't trigger actual DNS lookups or network connections.
Rather than reserving an entire TLD, the IETF reserved three specific second-level domains for documentation and examples: example.com, example.net, and example.org. These domains exist in the real DNS and resolve to real IP addresses, but they're reserved for documentation use.
When writing tutorials, configuration examples, or technical documentation, using example.com ensures you're not inadvertently directing traffic to someone's actual website. These domains won't change hands, won't host misleading content, and serve as universally recognized placeholders.
While not technically a TLD in the traditional sense, .local is reserved for Multicast DNS (mDNS) and link-local name resolution. Devices on local networks can advertise services under .local names (like printer.local or server.local) that other devices discover without requiring configured DNS servers.
Standard DNS resolution doesn't process .local queries, they're handled by mDNS protocols instead. This separation prevents conflicts between local network discovery and global DNS resolution.
.onion is reserved exclusively for Tor hidden services. These addresses aren't resolved through standard DNS but through the Tor network's onion routing system. The .onion reservation ensures that no one can register these domains in public DNS, which would create security vulnerabilities by potentially intercepting Tor traffic.
When you see a .onion address, you know it represents a Tor hidden service, not a conventional website accessible through normal internet routing.
Registry-Level Reserved Names
Beyond IETF special-use domains, individual TLD registries reserve certain second-level names for technical, legal, or policy reasons. These reservations vary by TLD but follow common patterns.
Many TLD registries reserve all two-character labels to prevent conflicts with country codes. Since country-code TLDs (ccTLDs) use two-letter codes like .us, .uk, and .de, reserving two-character second-level names in generic TLDs prevents confusion. You typically cannot register us.com or uk.net even though these strings aren't inherently invalid.
This reservation protects against confusion where users might mistake uk.com for a UK-specific domain rather than a .com domain about or referencing the UK.
Single-letter domains (like x.com or z.net) are often reserved or auctioned at premium prices rather than available through standard registration. Registries treat these as premium inventory due to their scarcity and memorability.
Some registries release single-character domains gradually, while others keep them permanently reserved. The policy varies by TLD and registry operator.
Pure numeric domain names face special restrictions in some TLDs. Since phone numbers are numeric, registries sometimes limit numeric domain registration to prevent conflicts with telephone routing or to reserve them for specific telecommunications uses.
Additionally, purely numeric domains can create security confusion in contexts where numbers might be interpreted as IP addresses rather than domain names.
Labels like nic, registry, whois, dns, and dns1 through dns4 are often reserved because registries use them for infrastructure services. The domain nic.example might host the registry's information center, while whois.example provides WHOIS services for the TLD.
Reserving these names prevents registrants from potentially disrupting registry operations or creating confusion about official registry services versus third-party domains.
Internationalizations of Reserved Terms
Registries operating internationalized domain name (IDN) TLDs often reserve translated versions of common reserved terms. If a TLD reserves "example" in English, it might also reserve the equivalent term in other languages relevant to that TLD's community.
This multilingual reservation prevents circumventing reserved name policies through language variations.
Technical Protocol Restrictions
Beyond explicit reservations, certain name characteristics create technical limitations on what can be registered or used effectively.
Labels Beginning or Ending with Hyphens
DNS labels cannot begin or end with hyphens except in specific circumstances (like internationalized domain names using Punycode encoding, which begin with "xn--"). A label like -example or test- violates DNS syntax rules and won't be accepted for registration.
This restriction prevents ambiguity in parsing and ensures consistent DNS label formatting across the internet.
Labels Exceeding Length Limits
DNS labels have a maximum length of 63 characters, and complete domain names cannot exceed 253 characters total. When you factor in domain registration requirements, extremely long labels simply aren't valid DNS names regardless of whether someone wants to register them. DNS labels traditionally support only alphanumeric characters and hyphens. While internationalized domain names expand this character set using encoding schemes, raw DNS still restricts which characters are valid in domain names.
Attempting to register domains containing spaces, special punctuation, or non-ASCII characters directly (without IDN encoding) will fail because they're syntactically invalid at the protocol level.
Security-Motivated Reservations
Some reservations exist primarily to prevent security issues or abuse.
Registries increasingly reserve strings that are visually confusable with existing high-value domains or could be used for phishing. While not universally implemented, some registries prevent registration of domains using characters that look similar to popular brands but differ in subtle ways.
IDN homograph attacks, where similar-looking characters from different scripts create visually identical domains, motivate many of these reservations. A domain using Cyrillic characters that looks identical to a major brand's Latin-character domain might be reserved to prevent impersonation.
Geographic and Government Terms
Many TLDs reserve geographic names (cities, regions, countries) and government-related terms to prevent misleading registrations. Terms like "government," "gov," "federal," or specific place names might be reserved to avoid creating confusion about official versus unofficial entities.
These reservations particularly apply in country-code TLDs where the registry has responsibility for protecting national interest and preventing misleading use of geographic or governmental terminology.
Some registries reserve extremely generic or high-value terms for auction, community use, or permanent reservation. Terms like "web," "internet," "online," or industry-specific keywords might not be available through standard registration channels.
This practice is controversial, some view it as registries extracting value from premium terms, while others see it as ensuring high-value names are allocated thoughtfully rather than on a first-come basis.
New gTLD Program Specific Reservations
ICANN's new generic TLD (gTLD) program introduced additional reservation requirements for all new TLDs launched since 2013.
ICANN-Mandated Reserved Names
All new gTLDs must reserve certain second-level names that ICANN specifies. This includes names related to ICANN functions, example names used in documentation, and terms that could create operational or security issues.
The list includes obvious candidates like icann, iana, and internic, but also extends to terms that might be needed for future protocol development or that have technical significance in internet operations.
Registry-Operator Reserved Names
In addition to ICANN-mandated reservations, registry operators can reserve additional names for their own operational needs, premium name programs, or policy reasons specific to their TLD's purpose and community.
For example, a TLD focused on a specific industry might reserve key industry terms for allocation through a curated process rather than open registration. A geographic TLD might reserve names of local significance.
Why These Restrictions Matter
Reserved name restrictions serve multiple essential purposes. They prevent technical conflicts where reserved names have specific protocol meanings, protect against security threats like phishing and impersonation, preserve namespace for future internet protocol development, and ensure critical infrastructure terms remain available for legitimate operational use.
Understanding these restrictions helps when planning domain registration strategies. If you're building a brand, testing whether your desired name is reserved across relevant TLDs saves time and frustration. For development and testing, knowing which special-use domains are available prevents accidentally using names that might conflict with real internet infrastructure. The reservation system also demonstrates the internet's governance model, balancing open registration with necessary restrictions, technical requirements with policy decisions, and immediate availability with long-term protocol stability.
Checking Reservation Status
Before investing effort in branding or infrastructure around a specific domain name, verify its availability. Most registrars provide lookup tools that show whether names are registered, available, reserved, or premium. For new TLDs, registry websites typically publish their complete reserved name lists.
When names are reserved, registries usually indicate why, whether it's an ICANN-mandated reservation, a registry policy reservation, or a technical restriction. This information helps you understand whether the reservation might change in the future or is permanent.
Some reserved names eventually become available through auctions, application processes, or policy changes. If a reserved name is critical to your needs, monitoring registry policies and participating in relevant community discussions might reveal future availability pathways.
The Broader Context
Reserved DNS names represent the careful stewardship required to maintain internet infrastructure. Every reservation balances competing interests: maximizing namespace availability, preventing abuse, supporting technical protocols, and protecting users from confusion or deception.
As the DNS namespace continues evolving with new TLDs, internationalized names, and changing technical requirements, reservation policies adapt. What's reserved today might become available tomorrow under new policies, while new reservations emerge to address newly discovered security or technical issues.
For organizations managing hosting infrastructure or email services, understanding reserved names prevents configuration mistakes and helps explain why certain domain names behave unexpectedly or aren't available for registration. The reserved name system ultimately serves everyone who uses the internet, ensuring that fundamental protocols work consistently, that local network configurations don't conflict with global infrastructure, and that malicious actors face obstacles when attempting impersonation or abuse. These restrictions, while occasionally frustrating when they prevent desired registrations, maintain the stability and security that make the internet's naming system reliable.
.png&w=2048&q=75)
.png&w=3840&q=75)