|Example domain||Type||Sponsoring institution|
|arpa||Infrastructure||Internet Architecture Board; restricted[clarification needed]|
|blue||Generic||Afilias Limited; unrestricted[clarification needed]|
|ovh||Generic||OVH SAS; run by AFNIC, unrestricted|
|name||Restricted generic||VeriSign Information Services, Inc.; unrestricted|
|ac||Country-code||Cable and Wireless (Ascension Island); unrestricted|
|zw||Country-code||Postal and Telecommunications Regulatory Authority of Zimbabwe; unrestricted|
|aero||Sponsored||Société Internationale de Télécommunications Aéronautiques; unrestricted|
A top-level domain (TLD) is one of the domains at the highest level in the hierarchical Domain Name System of the Internet after the root domain. The top-level domain names are installed in the root zone of the name space. For all domains in lower levels, it is the last part of the domain name, that is, the last non empty label of a fully qualified domain name. For example, in the domain name www.example.com, the top-level domain is com. Responsibility for management of most top-level domains is delegated to specific organizations by the ICANN, an Internet multi-stakeholder community, which operates the Internet Assigned Numbers Authority (IANA), and is in charge of maintaining the DNS root zone.
Originally, the top-level domain space was organized into three main groups: Countries, Categories, and Multiorganizations. An additional temporary group consisted of only the initial DNS domain, arpa, and was intended for transitional purposes toward the stabilization of the domain name system.
- Infrastructure top-level domain (ARPA): This group consists of one domain, the Address and Routing Parameter Area. It is managed by IANA on behalf of the Internet Engineering Task Force for various purposes specified in the Request for Comments publications.
- Generic top-level domains (gTLD): Top-level domains with three or more characters
- Generic restricted top-level domains (grTLD): These domains are managed under official ICANN accredited registrars.
- Sponsored top-level domains (sTLD): These domains are proposed and sponsored by private agencies or organizations that establish and enforce rules restricting the eligibility to use the TLD. Use is based on community theme concepts; these domains are managed under official ICANN accredited registrars.
- country-code top-level domains (ccTLD): Two-letter domains established for countries or territories. With some historical exceptions, the code for any territory is the same as its two-letter ISO 3166 code.
- Internationalized country code top-level domains (IDN ccTLD): ccTLDs in non-Latin character sets (e.g., Arabic, Cyrillic, Greek, Hebrew, or Chinese).
- Test top-level domains (tTLD): These domains were installed under .test for testing purposes in the IDN development process; these domains are not present in the root zone.
Countries are designated in the Domain Name System by their two-letter ISO country code; there are exceptions, however (e.g., .uk). This group of domains is therefore commonly known as country-code top-level domains (ccTLD). Since 2009, countries with non–Latin-based scripts may apply for internationalized country code top-level domain names, which are displayed in end-user applications in their language-native script or alphabet, but use a Punycode-translated ASCII domain name in the Domain Name System.
Internationalized country code TLDs
An internationalized country code top-level domain (IDN ccTLD) is a top-level domain with a specially encoded domain name that is displayed in an end user application, such as a web browser, in its language-native script or alphabet (such as the Arabic alphabet), or a non-alphabetic writing system (such as Chinese characters). IDN ccTLDs are an application of the internationalized domain name (IDN) system to top-level Internet domains assigned to countries, or independent geographic regions.
ICANN started to accept applications for IDN ccTLDs in November 2009, and installed the first set into the Domain Names System in May 2010. The first set was a group of Arabic names for the countries of Egypt, Saudi Arabia, and the United Arab Emirates. By May 2010, 21 countries had submitted applications to ICANN, representing 11 scripts.
The domain arpa was the first Internet top-level domain. It was intended to be used only temporarily, aiding in the transition of traditional ARPANET host names to the domain name system. However, after it had been used for reverse DNS lookup, it was found impractical to retire it, and is used today exclusively for Internet infrastructure purposes such as in-addr.arpa for IPv4 and ip6.arpa for IPv6 reverse DNS resolution, uri.arpa and urn.arpa for the Dynamic Delegation Discovery System, and e164.arpa for telephone number mapping based on NAPTR DNS records. For historical reasons, arpa is sometimes considered to be a generic top-level domain.
A set of domain names is reserved by the Internet Engineering Task Force as special-use domain names per authority of Request for Comments (RFC) 6761. The practice originated in RFC 1597 for reserved address allocations in 1994, and reserved top-level domains in RFC 2606 of 1999. RFC 6761 reserves the following four top-level domain names to avoid confusion and conflict. Any such reserved usage of those TLDs should not occur in production networks that utilize the global domain name system:
- example: reserved for use in examples
- invalid: reserved for use in invalid domain names
- localhost: reserved to avoid conflict with the traditional use of localhost as a hostname
- test: reserved for use in tests
RFC 7686 reserves the use of .onion for the self-authenticating names of Tor onion services. These names can only be resolved by a Tor client because of the use of onion routing to protect the anonymity of users.
Internet-Draft draft-wkumari-dnsop-internal-00 proposes reserving the use of .internal for "names which do not have meaning in the global context but do have meaning in a context internal to their network", and for which the RFC 6761 reserved names are semantically inappropriate.
In the late 1980s, InterNIC created the nato domain for use by NATO. NATO considered none of the then-existing TLDs as adequately reflecting their status as an international organization. Soon after this addition, however, InterNIC also created the int TLD for the use by international organizations in general, and persuaded NATO to use the second level domain nato.int instead. The nato TLD, no longer used, was finally removed in July 1996.
Other historical TLDs are cs for Czechoslovakia (now using cz for Czech Republic and sk for Slovakia), dd for East Germany (using de after reunification of Germany), yu for SFR Yugoslavia and Serbia and Montenegro (now using ba for Bosnia and Herzegovina, hr for Croatia, me for Montenegro, mk for North Macedonia, rs for Serbia and si for Slovenia), and zr for Zaire (now cd for the Democratic Republic of the Congo). In contrast to these, the TLD su has remained active despite the demise of the Soviet Union that it represents. Under the chairmanship of Nigel Roberts, ICANN's ccNSO is working on a policy for retirement of ccTLDs that have been removed from ISO 3166.
Around late 2000, ICANN discussed and finally introduced aero, biz, coop, info, museum, name, and pro TLDs. Site owners argued that a similar TLD should be made available for adult and pornographic websites to settle the dispute of obscene content on the Internet, to address the responsibility of US service providers under the US Communications Decency Act of 1996. Several options were proposed including xxx, sex and adult. The xxx top-level domain eventually went live in 2011.
During the 32nd International Public ICANN Meeting in Paris in 2008, ICANN started a new process of TLD naming policy to take a "significant step forward on the introduction of new generic top-level domains". This program envisioned the availability of many new or already proposed domains, as well as a new application and implementation process. Observers believed that the new rules could result in hundreds of new gTLDs being registered.
On 13 June 2012, ICANN announced nearly 2,000 applications for top-level domains, which began installation throughout 2013. The first seven – bike, clothing, guru, holdings, plumbing, singles, and ventures – were released in 2014.
Investigation into the conflicts was conducted at ICANN's request by Interisle Consulting. The resulting report was to become known as the Name Collision issue, which was first reported at ICANN 47.
Due to the structure of DNS, each node in the tree has its own collection of records, and since top-level domains are nodes in DNS, they have records of their own. For example, querying org itself (with a tool such as dig, host or nslookup) returns information on its nameservers:
QUESTION org. IN ANY ANSWER org. 21599 IN NS a0.org.afilias-nst.info. org. 21599 IN NS a2.org.afilias-nst.info. org. 21599 IN NS b0.org.afilias-nst.org. org. 21599 IN NS b2.org.afilias-nst.org. […]
Dotless domains are top-level domains that take advantage of that fact, and implement A, AAAA or MX DNS records to serve webpages or allow incoming email directly on a TLD – for example, a webpage hosted on http://example/, or an email address user@example.
ICANN and IAB have spoken out against the practice, classifying it as a security risk among other concerns. ICANN's Security and Stability Advisory Committee (SSAC) additionally claims that SMTP "requires at least two labels in the FQDN of a mail address" and, as such, mail servers would reject emails to addresses with dotless domains.
ICANN has also published a resolution in 2013 that prohibits the creation of dotless domains on gTLDs. ccTLDs, however, fall largely under their respective country's jurisdiction, and not under ICANN's. Because of this, there have been many examples of dotless domains on ccTLDs in spite of ICANN's vocal opposition.
As of August 2021, that is the case of Anguilla's .ai, online at http://ai./ (as a mirror of http://offshore.ai/), and of Uzbekistan's .uz, online at https://uz./ (as a mirror of https://cctld.uz/, albeit with an invalid certificate). Other ccTLDs with A or AAAA records, as of August 2021, include: .bh, .cm, .pn, .tk, .va, and .ws.
A similar query to org's presented above can be made for ai, which shows A and MX records for the TLD:
QUESTION ai. IN ANY ANSWER ai. 21599 IN A 126.96.36.199 ai. 21599 IN MX 10 mail.offshore.ai. ai. 21599 IN NS anycastdns1-cz.nic.ai. ai. 21599 IN NS anycastdns2-cz.nic.ai. ai. 21599 IN NS pch.whois.ai. […]
Following a 2014 resolution by ICANN, newly registered TLDs must implement the following A, MX, TXT, and SRV apex DNS records – where
<TLD> stands for the registered TLD – for at least 90 days:
<TLD>. 3600 IN MX 10 your-dns-needs-immediate-attention.<TLD>. <TLD>. 3600 IN SRV 10 10 0 your-dns-needs-immediate-attention.<TLD>. <TLD>. 3600 IN TXT "Your DNS configuration needs immediate attention see https://icann.org/namecollision" <TLD>. 3600 IN A 127.0.53.53
This requirement is meant to avoid domain name collisions when new TLDs are registered. For example, programmers may have used custom local domains such as foo.bar or test.dev, which would both collide with the creation of gTLDs .bar in 2014 and .dev in 2019. As of August 2021, top-level domains with these special apex records are .arab, .cpa, .politie, and .watches.
While this does create apex DNS records of type A and MX, they do not qualify as a dotless domain, as the records should not point to real servers. For instance, the A record contains the IP 127.0.53.53, a loopback address (see IPv4 § Addressing), picked as a mnemonic to indicate a DNS-related problem, as DNS uses port 53.
Several networks, such as BITNET, CSNET, and UUCP, existed that were in widespread use among computer professionals and academic users, but were not interoperable directly with the Internet and exchanged mail with the Internet via special email gateways. For relaying purposes on the gateways, messages associated with these networks were labeled with suffixes such as bitnet, oz, csnet, or uucp, but these domains did not exist as top-level domains in the public Domain Name System of the Internet.
Most of these networks have long since ceased to exist, and although UUCP still gets significant use in parts of the world where Internet infrastructure has not yet become well established, it subsequently transitioned to using Internet domain names, and pseudo-domains now largely survive as historical relics. One notable exception is the 2007 emergence of SWIFTNet Mail, which uses the swift pseudo-domain.
The anonymity network Tor formerly used the top-level pseudo-domain onion for Tor hidden services, which can only be reached with a Tor client because it uses the Tor onion routing protocol to reach the hidden service to protect the anonymity of users. However, the pseudo-domain became officially reserved in October 2015. i2p provides a similar hidden pseudo-domain, .i2p.
BT hubs use the top-level pseudo-domain .home for local DNS resolution of routers, modems and gateways.
- List of Internet top-level domains
- Alternative DNS root
- Domain hack
- Domain name registrar
- Public Suffix List
- Second-level domain
- "Delegation Record for .ARPA". iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 10 November 2015.
- "Delegation Record for .BLUE". www.iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 10 November 2015.
- "Why .BLUE?". Dotblue.blue. Archived from the original on 21 October 2014. Retrieved 10 November 2015.
- "Delegation Record for .OVH". www.iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 10 November 2015.
- "Delegation Record for .NAME". www.iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 10 November 2015.
- "Delegation Record for .AC". www.iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 10 November 2015.
- "Delegation Record for .ZW". www.iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 10 November 2015.
- "Delegation Record for .AERO". www.iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 10 November 2015.
- "Delegation Record for .ไทย". iana.org. Internet Corporation for Assigned Names and Numbers (ICANN). Retrieved 23 February 2017.
- Postel, Jon (March 1994). "Domain Name System Structure and Delegation". Request for Comments. Network Working Group. doi:10.17487/RFC1591. Retrieved 7 February 2011.
This memo provides some information on the structure of the names in the Domain Name System (DNS), specifically the top-level domain names; and on the administration of domains.
- Postel, J.; Reynolds, J. (October 1984). "Domain Requirements". Request for Comments. Network Working Group. doi:10.17487/RFC0920. Retrieved 7 February 2011.
- Postel, J. (October 1984). "Domain Name System Implementation Schedule - Revised". Request for Comments. Network Working Group. doi:10.17487/RFC0921. Retrieved 7 February 2011.
This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is an update of RFC-881, and RFC-897. This is an official policy statement of the IAB and the DARPA.
- "IANA root zone database". IANA.org. Internet Assigned Numbers Authority. Retrieved 10 November 2015.
- Codes for the Representation of Names of Countries, ISO-3166, International Organization for Standardization. (May 1981)
- "ICANN Bringing the Languages of the World to the Global Internet" (Press release). Internet Corporation For Assigned Names and Numbers (ICANN). 30 October 2009. Retrieved 30 October 2009.
- "'Historic' day as first non-Latin web addresses go live". BBC News. 6 May 2010. Retrieved 7 May 2010.
- "IANA-managed Reserved Domains". IANA. Retrieved 4 March 2022.
- "Special-Use Domain Names". IANA. Retrieved 3 March 2022.
- RFC 6761, Special-Use Domain Names, S. Cheshire, M. Krochmal, The Internet Society (February 2013)
- RFC 6762, Multicast DNS, S. Cheshire, M. Krochmal, The Internet Society (February 2013)
- RFC 7686, The ".onion" Special-Use Domain Name, J. Appelbaum, A. Muffett, The Internet Society (October 2015)
- "InterNIC FAQs on New Top-Level Domains". Internic.net. 25 September 2002. Retrieved 28 March 2013.
- RFC 3675: .sex Considered Dangerous
- (historical) gTLD MoU Archived 13 June 2008 at the Wayback Machine
- "32nd International Public ICANN Meeting". ICANN. 22 June 2008.
- "New gTLD Program". ICANN. Retrieved 15 June 2009.
- ICANN Board Approves Sweeping Overhaul of Top-level Domains, CircleID, 26 June 2008.
- "The Top 10 Proposed New Top Level Domains So Far". Retrieved 12 June 2012.
- "Reveal Day 13 June 2012 – New gTLD Applied-For Strings". Newgtlds.icann.org. Archived from the original on 15 June 2012. Retrieved 28 March 2013.
- "What the new top-level domains from ICANN mean for you - Digital Trends". Digital Trends. 5 February 2014.
- "Name Collision". ICANN Wiki. Retrieved 5 July 2021.
- "ICANN 47". ICANN Wiki. Retrieved 5 July 2021.
- "SSAC Report on Dotless Domains". ICANN. 24 August 2012. Retrieved 14 August 2021.
- "IAB Statement: Dotless Domains Considered Harmful". Internet Architecture Board. 2013. Retrieved 14 August 2021.
- "Approved Resolutions | Meeting of the New gTLD Program Committee".
- Levine, John; Hoffman, Paul (December 2013). "Top-Level Domains That Are Already Dotless". Internet Engineering Task Force. Retrieved 14 August 2021.
- Atallah, Akram (4 August 2014). "Name Collision Occurrence Assessment". ICANN. Retrieved 17 August 2021.
- "Name Collision Resources & Information". ICANN. Retrieved 17 August 2021.
- "SWIFTNet Mail now available". SWIFT. 16 May 2007. Retrieved 3 January 2010.
- Addressing the World: National Identity and Internet Country Code Domains, edited by Erica Schlesinger Wass (Rowman & Littlefield, 2003, ISBN 0-7425-2810-3) examines connections between cultures and their ccTLDs.
- Ruling the Root by Milton Mueller (MIT Press, 2001, ISBN 0-262-13412-8) discusses TLDs and domain name policy more generally.