Top-level domain

From Infogalactic: the planetary knowledge core
(Redirected from Top level domain)
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

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.[1]
blue generic Afilias Limited; unrestricted.[2][3]
ovh generic OVH SAS; run by AFNIC, unrestricted.[4]
name restricted generic VeriSign Information Services, Inc.; unrestricted.[5]
ac country-code Cable and Wireless (Ascension Island); unrestricted.[6]
zw country-code Postal and Telecommunications Regulatory Authority of Zimbabwe; unrestricted.[7]
aero sponsored Societe Internationale de Telecommunications Aeronautique; unrestricted.[8]
テスト test Internet Assigned Numbers Authority; domain is not present in the root zone (as of 2015).[9]

A top-level domain (TLD) is one of the domains at the highest level in the hierarchical Domain Name System of the Internet.[10] 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.

History

Originally, the top-level domain space was organized into three main groups: Countries, Categories, and Multiorganizations.[11] An additional temporary group consisted of only the initial DNS domain, arpa,[12] and was intended for transitional purposes toward the stabilization of the domain name system.

Types

As of 2015, IANA distinguishes the following groups of top-level domains:[13]

Countries are designated in the Domain Name System by their two-letter ISO country code;[14] 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.

Generic top-level domains (formerly Categories) initially consisted of gov, edu, com, mil, org, and net. More generic TLDs have been added, such as info.

The authoritative list of currently existing TLDs in the root zone is published at the IANA website at https://www.iana.org/domains/root/db/.

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,[15] 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.[16]

IDN test domains

In the process of testing internationalized top-level domains, ICANN implemented a set of IDN top-level domains that are translations of the name example.test into various languages in their respective scripts.

DNS name Link Script Language
xn--mgbh0fb.xn--kgbechtv http://مثال.إختبار Arabic Arabic
xn--fsqu00a.xn--0zwm56d http://例子.测试 Simplified Chinese Chinese
xn--fsqu00a.xn--g6w251d http://例子.測試 Traditional Chinese Chinese
xn--hxajbheg2az3al.xn--jxalpdlp http://παράδειγμα.δοκιμή Greek Greek
xn--p1b6ci4b4b3a.xn--11b5bs3a9aj6g http://उदाहरण.परीक्षा Devanagari Hindi
xn--r8jz45g.xn--zckzah http://例え.テスト Kanji+Kana Japanese
xn--9n2bp8q.xn--9t4b11yi5a http://실례.테스트 Hangul Korean
xn--mgbh0fb.xn--hgbk6aj7f53bba http://مثال.آزمایشی Perso-Arabic Persian
xn--e1afmkfd.xn--80akhbyknj4f http://пример.испытание Cyrillic Russian
xn--zkc6cc5bi7f6e.xn--hlcj6aya9esc7a http://உதாரணம்.பரிட்சை Tamil Tamil
xn--6dbbec0c.xn--deba0ad http://דוגמה.טסט Hebrew Hebrew
xn--fdbk5d8ap9b8a8d.xn--deba0ad http://בײַשפּיל.טסט Hebrew Yiddish

These testing domains were terminated on 31 October 2013.[17]

Infrastructure domain

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.

Reserved domains

RFC 6761 reserves the following four top-level domain names to avoid confusion and conflict.[18] 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
  • onion: (unofficial) reserved for the use of the Tor anonymity network, for access to Tor hidden services

In addition, RFC 6762 reserves the use of .local for link-local host names that can be resolved via the Multicast DNS name resolution protocol.[19]

Historical domains

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.

Proposed domains

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Around late 2000 when ICANN discussed and finally introduced[20] 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.[21] The .xxx domain went live in 2011.

An older proposal[22] consisted of seven new gTLDs: arts, firm, info, nom, rec, shop, and web. Later biz, info, museum, and name covered most of these old proposals.

During the 32nd International Public ICANN Meeting in Paris in 2008,[23] 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 envisions the availability of many new or already proposed domains, as well as a new application and implementation process.[24] Observers believed that the new rules could result in hundreds of new gTLDs being registered.[25] Proposed TLDs included free, music, shop, berlin, wien and nyc.

On 13 June 2012 ICANN has revealed nearly 2,000 applications for new top-level domains, which began to go live throughout 2013 after thorough examination.[26][27] Donuts Inc. has invested $57 million in more than 300 applications[28][29] while Famous Four Media applied for 61 new strings.[30] The first seven – .bike, .clothing, .guru, .holdings, .plumbing, .singles, and .ventures – are already live, and all belong to Donuts. More have been released throughout 2014 and will continue coming online steadily into 2015.[31]

Alternative DNS roots

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

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.

Pseudo-domains

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

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.[32]

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.

See also

Further reading

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Codes for the Representation of Names of Countries, ISO-3166, International Organization for Standardization. (May 1981)
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. RFC 6761, Special-Use Domain Names, S. Cheshire, M. Krochmal, The Internet Society (February 2013)
  19. RFC 6762, Multicast DNS, S. Cheshire, M. Krochmal, The Internet Society (February 2013)
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. RFC 3675: .sex Considered Dangerous
  22. (historical) gTLD MoU
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. ICANN Board Approves Sweeping Overhaul of Top-level Domains, CircleID, 26 June 2008.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.

External links