Top-level domain(Redirected from Top level domain)
|For a full list of about 1,000 TLDs, see List of Internet top-level domains|
|Example domain||Type||Sponsoring institution|
|arpa||Infrastructure||Internet Architecture Board; restricted|
|blue||Generic||Afilias Limited; unrestricted|
|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||Societe Internationale de Telecommunications Aeronautique; unrestricted|
A top-level domain (TLD) is one of the domains at the highest level in the hierarchical Domain Name System of the Internet. 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 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 Internet Corporation for Assigned Names and Numbers (ICANN), which operates the Internet Assigned Numbers Authority (IANA), and is in charge of maintaining the DNS root zone.
IANA currently distinguishes the following groups of top-level domains:
- country-code top-level domains (ccTLD)
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.
As of 2015, IANA distinguishes the following groups of top-level domains:
- 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
- restricted generic 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, 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 TLDsEdit
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.
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 obviously 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 hidden services. These names can only be resolved by a Tor client because of the use of onion routing to protect the anonymity of users.
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 Slovak Republic), dd for East Germany (using de after reunification of Germany), yu for SFR Yugoslavia (now using ba for Bosnia and Herzegovina, hr for Croatia, me for Montenegro, mk for Macedonia, rs for Serbia and si for Slovenia), and zr for Zaire (now cd for 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.
Around late 2000 when 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 and 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 domain 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. Proposed TLDs included free, music, shop, berlin, wien, nyc and istanbul
On 13 June 2012 ICANN announced nearly 2,000 applications for top-level domains, which began installation throughout 2013. Donuts Inc. invested $57 million in more than 300 applications while Famous Four Media applied for 61 new domains. The first seven, bike, clothing, guru, holdings, plumbing, singles, and ventures are active. More were released in 2014 and 2015.
Alternative DNS rootsEdit
ICANN's slow progress in creating new generic top-level domains, and the high application costs associated with TLDs, contributed to the creation of alternate DNS roots with different sets of top-level domains. Such domains may be accessed by configuration of a computer with alternate or additional (forwarder) DNS servers or plugin modules for web browsers. Browser plugins detect alternate root domain requests and access an alternate domain name server for such requests.
Several networks, such as BITNET, CSNET, 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.
- 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.
- "Why .BLUE?". Dotblue.blue. Retrieved 10 November 2015.
- "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.
- "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. 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.
- "Root Zone Database". Interxxx Assigned Numbers Authority.
- Postel, J.; Reynolds, J. (October 1984). "Domain Requirements". Request for Comments. Network Working Group. Retrieved 7 February 2011.
- Postel, J. (October 1984). "Domain Name System Implementation Schedule - Revised". Request for Comments. Network Working Group. 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 2015-11-10.
- 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.
- 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. 2002-09-25. Retrieved 2013-03-28.
- RFC 3675: .sex Considered Dangerous
- (historical) gTLD MoU
- "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. Retrieved 2013-03-28.
- "Donuts full application list" (PDF). Donuts Inc. Archived from the original (PDF) on 28 March 2014. Retrieved 18 August 2013.
- Natasha Singer (17 August 2013). "When You Can’t Tell Web Suffixes Without a Scorecard". The New York Times. Retrieved 18 August 2013.
- "List of 61 new strings applied for Famous Four Media". domaintyper.com.
- "What the new top-level domains from ICANN mean for you - Digital Trends". Digital Trends. 5 February 2014.
- "SWIFTNet Mail now available". SWIFT. 16 May 2007. Retrieved 3 January 2010.