Atop-level domain (TLD) is one of thedomains at the highest level in the hierarchicalDomain Name System of theInternet after the root domain.[1] The top-level domain names are installed in theroot zone of the name space. For all domains in lower levels, it is the last part of thedomain name, that is, the last non-empty label of afully qualified domain name. For example, in the domain namewww.example.com, the top-level domain is.com. Responsibility for management of most top-level domains is delegated to specific organizations by theICANN, an Internet multi-stakeholder community, which operates theInternet Assigned Numbers Authority (IANA), and is in charge of maintaining theDNS root zone.
Originally, the top-level domain space was organized into three main groups:Countries,Categories, andMultiorganizations.[2] An additionaltemporary group consisted of only the initial DNS domain,.arpa,[3] and was intended for transitional purposes toward the stabilization of the domain name system.
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.
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 theirtwo-letter ISO country code;[5] there are exceptions, however (e.g.,.uk). This group of domains is, therefore, commonly known ascountry-code top-level domains (ccTLD). Since 2009, countries with non–Latin-based scripts may apply forinternationalized country code top-level domain names, which are displayed in end-user applications in their language-native script or alphabet, but use aPunycode-translated ASCII domain name in the Domain Name System.
Generic top-level domains (formerlycategories) initially consisted of.gov,.edu,.com,.mil,.org, and.net. More generic TLDs have been added, such as.info.
ICANN started to accept applications for IDN ccTLDs in November 2009,[6] 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.[7]
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 forreverse DNS lookup, it was found impractical to retire it, and is used today exclusively for Internet infrastructure purposes such as in-addr.arpa forIPv4 and ip6.arpa for IPv6 reverse DNS resolution, uri.arpa and urn.arpa for theDynamic Delegation Discovery System, and e164.arpa fortelephone number mapping based onNAPTR DNS records. For historical reasons,.arpa is sometimes considered to be a generic top-level domain.[8]
A set of domain names is reserved[9][10] by the Internet Engineering Task Force asspecial-use domain names. The practice originated in RFC 1597 for reserved address allocations in 1994 and reserved top-level domains in RFC 2606 of 1999, with additional reservations in later RFCs. These reserved names should not be used in production networks that utilize the global domain name system.
In the late 1980s,InterNIC created the.nato domain for use byNATO.[citation needed] NATO considered none of the then-existing TLDs as adequately reflecting their status as aninternational 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 domainnato.int instead. Thenato TLD, no longer used, was finally removed in July 1996.[citation needed]
Around late 2000,ICANN discussed and finally introduced[17].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 USCommunications Decency Act of 1996. Several options were proposed includingxxx,sex andadult.[18] The.xxx top-level domain eventually went live in 2011.[19]
An older proposal consisted of seven new gTLDs: arts, firm,.info, nom, rec,.shop, and.web.[20] Later.biz,.info,.museum, and.name covered most of these old proposals.
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".[21] This program envisioned the availability of many new or already proposed domains, as well as a new application and implementation process.[22] Observers believed that the new rules could result in hundreds of new gTLDs being registered.[23]
On 13 June 2012,ICANN announced nearly 2,000 applications for top-level domains, which began installation throughout 2013.[24][25] The first seven –bike,clothing,guru,holdings,plumbing,singles, andventures – were released in 2014.[26]
ICANN rejected several proposed domains to include.home and.corp due to conflicts regarding gTLDs that are in use in internal networks.
Investigation into the conflicts was conducted at ICANN's request byInterisle Consulting. The resulting report was to become known as the Name Collision[27] issue, which was first reported at ICANN 47.[28]
.org[.] is a node in the DNS tree, just likewikipedia.[org.] anden.[wikipedia.org.]. As such, it has its ownDNS records.
Due to the structure ofDNS, each node in the tree has its own collection ofrecords, and since top-level domains are nodes in DNS, they have records of their own. For example, queryingorg itself (with a tool such asdig,host, ornslookup) returns information on itsnameservers:
Dotless domains are top-level domains that take advantage of that fact, and implementA,AAAA orMX DNS records to serve webpages or allow incoming email directly on a TLD – for example, a webpage hosted onhttp://example/, or an email addressuser@example.[29]
ICANN andIAB have spoken out against the practice, classifying it as a security risk among other concerns.[30] ICANN's Security and Stability Advisory Committee (SSAC) additionally claims thatSMTP "requires at least two labels in theFQDN of a mail address" and, as such, mail servers would reject emails to addresses with dotless domains.[29]
ICANN has also published a resolution in 2013 that prohibits the creation of dotless domains ongTLDs.[31]ccTLDs, however, fall largely under their respective country'sjurisdiction, 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.
Historically, many other ccTLDs have had A or AAAA records. On 3 September 2013, as reported by theIETF, they were the following:[32].ac,.dk,.gg,.io,.je,.kh,.sh,.tm,.to, and.vi.
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:[33]
<TLD>.3600INMX10your-dns-needs-immediate-attention.<TLD>.<TLD>.3600INSRV10100your-dns-needs-immediate-attention.<TLD>.<TLD>.3600INTXT"Your DNS configuration needs immediate attention see https://icann.org/namecollision"<TLD>.3600INA127.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 asfoo.bar ortest.dev, which would both collide with the creation of gTLDs.bar in 2014 and.dev in 2019.
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 (seeIPv4 § Addressing), picked as a mnemonic to indicate a DNS-related problem, asDNS uses port 53.[34]
Several networks, such asBITNET,CSNET, andUUCP, 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 publicDomain 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 ofSWIFTNet Mail, which uses the swift pseudo-domain.[35]
The anonymity networkTor formerly used the top-level pseudo-domain.onion foronion services, which can only be reached with a Tor client because it uses the Toronion routing protocol to reach the hidden service to protect the anonymity of users. However, the pseudo-domain became officially reserved in October 2015.[36]i2p provides a similar hidden pseudo-domain, .i2p,[37] andNamecoin uses the .bit pseudo-domain.[38]
^Postel, Jon (March 1994)."Domain Name System Structure and Delegation".Request for Comments. Network Working Group.doi:10.17487/RFC1591. Retrieved7 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. (October 1984)."Domain Name System Implementation Schedule - Revised".Request for Comments. Network Working Group.doi:10.17487/RFC0921. Retrieved7 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.
Addressing the World:National Identity and Internet Country Code Domains, edited by Erica Schlesinger Wass (Rowman & Littlefield, 2003,ISBN0-7425-2810-3) examines connections between cultures and their ccTLDs.
