TLD

TLD (top-level domain), also called a Top-Level Domain, is the rightmost label in a fully qualified domain name — the segment that follows the last dot. In www.example.com, the TLD is .com; in bbc.co.uk, it is .uk. TLDs sit at the apex of the DNS hierarchy and are the foundation upon which every other domain name is built.

Where the TLD sits in a domain name

The DNS is a hierarchical, tree-structured naming system. Reading a domain name from right to left reveals that hierarchy:

1. Root (.) — The invisible dot at the very right end. The root zone is the authoritative starting point: a small set of servers maintained by IANA that know which name servers are authoritative for every TLD.
2. TLD — The first visible label from the right (.com, .org, .de). Each TLD has its own authoritative name servers, run by a registry operator.
3. Second-level domain — The label immediately left of the TLD (e.g., example in example.com). This is what registrants purchase from a registrar.
4. Subdomain — Any further labels to the left (www, mail, blog), managed by whoever controls the second-level domain.

When a resolver looks up www.example.com, it first asks a root server where .com lives, then asks the .com registry name servers where example.com lives, then asks example.com's name servers for the www record. This delegation chain ensures that no single server needs to know all domain names.

Types of TLD

IANA groups TLDs into several categories:

The .arpa domain is the only current infrastructure TLD. It hosts reverse-lookup zones (in-addr.arpa for IPv4, ip6.arpa for IPv6) that map IP addresses back to host names.

Country-code TLDs were originally scoped to registrants within the named country, but many have been liberalised for global registration — .io (British Indian Ocean Territory) and .co (Colombia) are prominent examples used internationally as generic alternatives.

How TLDs are created and delegated

The authoritative list of all delegated TLDs is maintained in the IANA root zone database (iana.org/domains/root/db), which maps each TLD to its set of authoritative name servers and its designated registry operator.

ccTLD delegation follows the policy set out in RFC 1591 (Postel, 1994): two-letter codes are derived from ISO 3166-1, and each is delegated to a trustee — typically a government agency or nationally recognised body — that is expected to serve the public interest of that country or territory. IANA reviews requests for re-delegation when governance of a ccTLD changes hands.

New gTLDs are created through ICANN application rounds. The first major expansion began in 2012, when ICANN opened applications for any string of three or more characters as a generic TLD. Applicants pay a base fee, undergo evaluation for technical capability and financial stability, pass an objection process (covering community, morality, intellectual-property, and string-confusion grounds), and sign a Registry Agreement with ICANN (ICANN new gTLD programme). Over 1,200 new gTLDs were delegated from that round. A second application round opened in 2026, further expanding the namespace.

Once delegated, a TLD's registry operator maintains the authoritative database of all second-level domains registered under it, runs the zone's name servers, and sets the policies (pricing, eligibility, length rules) that registrars must follow when selling names to registrants.

Examples and notable TLDs

TLDs, value, and SEO

Search engines treat TLDs in two distinct ways:

Geo-targeting: A ccTLD sends a geographic signal. Google Search Central notes that a .de site is generally interpreted as targeting German-speaking users, and Google Search Console allows explicit geo-targeting for generic TLDs but applies ccTLD signals automatically. If a business intends to serve a global audience from a single domain, a generic TLD avoids unintended geographic restriction.

Ranking: For most purposes, the TLD itself is not a ranking factor. Google has stated that it treats new gTLDs like any other TLD and that a .com does not inherently outrank a .app or .xyz. What matters is the overall authority and relevance of the domain, not the extension alone. Some older keyword-rich TLDs (like .jobs or .travel) carry implicit context signals, but these are minor compared to content quality and backlink profile.

Brand perception and memorability: Domain investors and marketers observe that established short TLDs — especially .com — carry strong end-user recognition, which can affect click-through rates in search results, direct navigation, and trust. This is a market and behavioural dynamic rather than an algorithmic one.

Premium and aftermarket pricing: The perceived value of a TLD affects secondary-market prices for second-level domain names beneath it. .com names command higher aftermarket prices on average than equivalent names under newer extensions, reflecting consumer familiarity rather than any technical advantage.

TLDs and tokenized domains

Several blockchain-based naming systems operate outside the IANA root zone, effectively introducing alternative TLDs that resolve only within compatible resolvers or browser extensions. Examples include .eth (Ethereum Name Service), .crypto, and .nft. These are not delegated through IANA and do not resolve in the global DNS by default, though bridges and gateway services can provide partial interoperability.

Within the IANA-administered namespace, tokenization of second-level domain names (representing ownership of a name like example.com as a blockchain token) is a separate concept from the TLD itself; the TLD remains under the same registry governance regardless of how ownership of individual names beneath it is recorded.