Generic top-level domain

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by SGGH (talk | contribs) at 20:06, 7 June 2008 (Removing backlinks to .sport that has been speedily deleted per (CSD G11); using TW). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

A generic top-level domain (gTLD) is a top-level domain used (at least in theory) by a particular class of organization. These are three or more letters long, and are named for the type of organization that they represent (for example, .com for commercial organizations). The following gTLDs currently exist[1] (as does .arpa, which is sometimes considered a gTLD):

gTLD intended use
.aero the air transport industry.
.asia companies. organisations and individuals in the Asia-Pacific region
.biz business use
.cat Catalan language/culture
.com commercial organizations, but unrestricted
.coop cooperatives
.edu post-secondary educational establishments
.gov government entities within the United States at the federal, state, and local levels
.info informational sites, but unrestricted
.int international organizations established by treaty
.jobs employment-related sites
.mil the U.S. military
.mobi sites catering to mobile devices
.museum museums
.name families and individuals
.net originally for network infrastructures, now unrestricted
.org originally for organizations not clearly falling within the other gTLDs, now unrestricted
.pro certain professions
.tel services involving connections between the telephone network and the Internet (added March 2, 2007)
.travel travel agents, airlines, hoteliers, tourism bureaus, etc.

The following gTLDs are in the process of being approved, and may be added to the root nameservers in the near future:

  • .post - for postal services
  • .geo - for geographically related sites
  • .cym - for Welsh language/culture
  • .sco - for Scots language/culture

History

When generic top-level domains were first implemented, in January 1985, there were six:


While .net was not listed in the original RFC document describing the domain name system, it was added by the time the first group of names were implemented.

The .com, .net, and .org gTLDs, despite their original different uses, are now in practice open for use by anybody for any purpose.

In November 1988, another gTLD was introduced, .int. This gTLD was introduced in response to NATO's request for a domain name which adequately reflected its character as an international organization. It was also originally planned to be used for some Internet infrastructure databases, such as .ip6.int, the IPv6 equivalent of .in-addr.arpa. However, in May 2000, the Internet Architecture Board proposed to close the .int domain to new infrastructure databases. All future such databases would be created in .arpa (a legacy of the pre-TLD system), and existing ones would move to .arpa wherever feasible, which led to the use of .ip6.arpa for IPv6 reverse lookups.

By the mid-1990s there was pressure for more gTLDs to be introduced. Jon Postel, as head of IANA, invited applications from interested parties.[2] In early 1995, Postel created "Draft Postel", an Internet draft containing the procedures to create new domain name registries and new TLDs. Draft Postel created a number of small committees to approve the new TLDs. Because of the increasing interest, a number of large organizations took over the process under the Internet Society's umbrella. This second attempt involved the setting up of a temporary organization called the International Ad Hoc Committee (IAHC). On February 4 1997, the IAHC issued a report ignoring the Draft Postel recommendations and instead recommended the introduction of seven new gTLDs (.arts, .firm, .info, .nom, .rec, .store, and .web). However, progress on this stalled after the U.S. government intervened and nothing ever came of it.

In October 1998, the Internet Corporation for Assigned Names and Numbers (ICANN) formed to take over the task of managing domain names. After a call for proposals (August 15, 2000) and a brief period of public consultation, ICANN announced on November 16, 2000 its selection of the following seven new gTLDs:

These new gTLDs started to come into use in June 2001, and by the end of that year all except .pro existed, with .biz, .info and .museum already in full operation. .name and .coop became fully operational in January 2002, and .aero followed later in the year. .pro became a gTLD in May 2002, but did not become fully operational until June 2004.

ICANN is adding further gTLDs, starting with a set of sponsored top-level domains (like the previous .aero, .coop, and .museum). The application period for these lasted from 15 December 2003 until 16 March 2004, and resulted in ten applications. As of June 2005, ICANN had announced the approval in principle of several new TLDs, with details still being worked out and implementation still in the future:

Proposals for .mail were still under consideration. There was also a second proposal for .tel.

Unofficial TLDs and proposals

Various organizations and businesses have proposed additional TLDs, and some have created unofficial implementations of them, which are not generally functional. These include .nyc, .berlin,[3] .sco,[4] .gal,[5] .bzh,[6],.sport[7] and many others.

Pseudo top-level domains

A number of pseudo top-level domains have been defined at various times. Although these pseudo-TLDs look like top-level domains, and serve the same syntactic function in creating names for network endpoints, they have no meaning in the global Domain Name System and are (or were) used only for specialist purposes. These "pseudo-TLDs" include .bitnet, .csnet, .local, .onion and .uucp.

Although they have no official status, they are generally regarded as having been unofficially "grandfathered", and are unlikely ever to be allocated as top-level domains.

Alternative DNS roots

A number of companies have set up their own DNS systems which purport to expand or replace the official DNS root system, and thus to provide their own top-level domains. The article alternative DNS root covers these in more detail.

References

External links