A TLD, Top-Level Domain, is the rightmost segment of a domain name, appearing after the final dot. In example.com the TLD is .com. In redirect.supply the TLD is .supply. In bbc.co.uk the TLD is .uk: with .co being a second-level domain within the .uk namespace. TLDs sit at the top of the DNS hierarchy, immediately below the DNS root, and define the highest-level category or geographic association of a domain name.

Every domain name has exactly one TLD. The TLD is the first decision in domain registration, it defines which registry manages the domain, what rules apply to registration, and often shapes perceptions of the website’s purpose, audience, and geographic focus. .com signals commercial and global intent. .gov signals a government entity. .de signals a German audience. .io signals a technology product. The TLD is the most visible categorisation signal in a domain name.

TLDs are managed by ICANN, the Internet Corporation for Assigned Names and Numbers, which delegates authority for each TLD to a registry operator. The registry operator maintains the list of all registered domains under the TLD, sets registration policies, and operates the nameservers that serve the TLD zone. Domain registrars are accredited by ICANN to sell registrations under TLDs on behalf of registry operators.

How TLDs work in DNS

TLDs occupy a specific layer in the DNS hierarchy: the level immediately below the root. When a DNS resolver performs a lookup for example.com it queries root nameservers which return the nameservers for the .com TLD zone. The resolver then queries the .com TLD nameservers which return the NS records for example.com: delegating to the domain’s authoritative nameservers.

Every TLD has its own DNS zone managed by the TLD registry. The .com zone contains delegation records for every registered .com domain. The .uk zone contains delegations for every registered .uk domain. The TLD zone holds only delegation records, NS records pointing to each domain’s authoritative nameservers, not the actual DNS records for individual domains.

When a new domain is registered the registrar submits the domain and its nameserver information to the TLD registry. The registry adds the delegation NS records to the TLD zone, making the domain resolvable in DNS. When nameservers change the registrar updates the TLD zone records. When a domain expires the delegation records are removed.

The TLD zone is served by the TLD registry’s nameservers, separate infrastructure from the root nameservers and from individual domain nameservers. The .com TLD is served by Verisign’s nameservers, some of the most queried DNS infrastructure in the world given the enormous volume of .com domains.

Types of TLDs

TLDs fall into several categories reflecting their intended purpose, geographic association, sponsoring organisation, or historical context.

Generic TLDs, gTLDs: TLDs without geographic restriction available for general use. The original set of gTLDs established in the 1980s includes .com, .net, .org, .edu, .gov, .mil, and .int. These original TLDs had intended audiences, .com for commercial entities, .net for network infrastructure, .org for non-profit organisations, but most restrictions were never enforced. .com became universally dominant for commercial websites regardless of type.

.edu and .gov maintain restricted registration, .edu requires accredited US educational institutions and .gov requires US government entities. .com, .net, and .org are open registration, anyone can register regardless of organisation type or purpose.

New gTLDs: ICANN launched a new gTLD program starting in 2012 that dramatically expanded the TLD namespace. Hundreds of new TLDs were introduced, .app, .dev, .store, .online, .shop, .tech, .io, .co, .supply, .agency, .design, and many others. New gTLDs provide alternatives to the saturated .com namespace where desirable short names are largely unavailable. They also enable more descriptive domain names, redirect.supply is more descriptive than redirectsupply.com.

Country code TLDs, ccTLDs: two-letter TLDs assigned to specific countries and territories based on the ISO 3166-1 standard. .uk for the United Kingdom, .de for Germany, .fr for France, .jp for Japan, .au for Australia, .ca for Canada, .us for the United States. ccTLDs are managed by national registry operators and may have residency or local presence requirements for registration.

Some ccTLDs have become popular for generic use beyond their assigned country because of their letter combinations. .io: assigned to the British Indian Ocean Territory, is widely used by technology companies and startups. .co: Colombia, is used as a .com alternative. .tv: Tuvalu, is used for video and media. .me: Montenegro, is used for personal sites and applications. .ai: Anguilla, has become popular with AI companies. The country of assignment often receives significant revenue from these generic uses of their ccTLD.

Internationalised TLDs, IDN TLDs: TLDs written in non-Latin scripts enabling domain names in Arabic, Chinese, Cyrillic, Hindi, and other writing systems. .中国 for China, .рф for Russia, .مصر for Egypt. IDN TLDs allow native-script domain names for audiences that use non-Latin alphabets, important for accessibility and localisation in non-English-speaking markets.

Sponsored TLDs, sTLDs: TLDs operated by specific sponsoring organisations for defined communities with eligibility requirements. .edu for accredited US educational institutions, .gov for US government entities, .mil for the US military, .aero for the aviation industry, .museum for museums, .coop for cooperatives. The sponsoring organisation sets registration policies that restrict eligibility to the intended community.

TLD selection for new domains

Choosing a TLD is one of the most consequential decisions in domain registration, it affects memorability, trust, SEO, and the practical availability of desirable names.

.com as the default: .com remains the most widely recognised, most trusted, and most expected TLD for commercial websites globally. When people think of a website they typically assume .com unless told otherwise. The .com expectation is so strong that typing a domain name in many browsers automatically appends .com if no TLD is specified. For organisations with a global audience and commercial focus .com is generally the preferred TLD when a desirable name is available.

The availability problem with .com is real, most short, memorable, dictionary-word .com domains are registered. Desirable .com names available for standard registration are increasingly rare. This has driven interest in alternatives.

New gTLDs as alternatives: new gTLDs like .io, .co, .app, .dev, .store, and many others provide availability that .com cannot. A company that cannot get redirect.com might register redirect.supply or redirect.io. New gTLDs are increasingly accepted, particularly in technology circles where .io has become a standard choice, but .com still commands more universal recognition.

ccTLDs for geographic targeting: organisations primarily serving a specific country benefit from the corresponding ccTLD. example.de signals to German users and search engines that the site is specifically for the German market. Google uses ccTLDs as a geographic targeting signal, a site on .de is understood to target Germany even without other localisation signals.

Consistency across TLDs for brand protection: registering a domain name across multiple TLDs, example.com, example.net, example.org, example.io: protects the brand from competitors and bad actors registering similar names on alternative TLDs. These brand protection registrations are then redirected to the primary domain, a common domain parking and redirect management use case.

TLDs and SEO

The TLD itself has minimal direct impact on search rankings, Google has stated that new gTLDs are treated the same as .com and other established TLDs in ranking algorithms. A well-built site on .supply ranks on the same basis as a well-built site on .com: content quality, backlinks, and technical factors determine rankings, not TLD choice.

The indirect effects of TLD choice on SEO are more significant.

User trust and click-through rates: users are more likely to click on .com results in search listings because .com is the most familiar and trusted TLD. A less familiar TLD may receive lower click-through rates even at identical ranking positions, which can affect rankings over time as Google uses engagement signals. This is more a human psychology factor than an algorithmic factor.

ccTLD geographic signals: country code TLDs send strong geographic targeting signals that help sites rank in their target country’s search results. example.de ranks more easily in Germany than example.com targeting Germany. For businesses focused on a specific national market the corresponding ccTLD is an SEO advantage for local search.

Link juice across TLDs: backlinks from any TLD pass SEO equity equally, a link from a .io site is treated the same as a link from a .com site in ranking algorithms. The TLD of the linking domain does not affect the value of the link.

Brand protection and redirect management: permanent redirects from brand protection TLD registrations to the primary domain consolidate any backlinks or traffic from those alternative TLDs. A backlink pointing to example.net passes its equity to example.com through the redirect, ensuring brand protection registrations contribute positively rather than simply sitting unused.

TLDs and redirect management

TLD management intersects with redirect management in several important ways.

Multi-TLD redirect configurations: organisations registering the same name across multiple TLDs need redirect rules for each non-primary TLD. example.net, example.org, example.io, and example.co all permanently redirect to example.com. Each redirect requires its own DNS configuration, connecting each domain to redirect infrastructure, and a global redirect rule pointing to the primary domain.

Managing multiple TLD redirects centrally, through a single redirect management platform, is more efficient than configuring each independently. All non-primary TLD domains are connected to the same redirect infrastructure with the same destination. Adding a new brand protection registration requires only connecting the new domain and configuring one redirect rule.

Domain rebranding across TLDs: when a company rebrands and moves to a new domain name it may also change TLDs, from oldbrand.com to newbrand.io for example. Both the old domain name and the old TLD change simultaneously. Permanent redirects from the old domain, regardless of TLD, to the new domain preserve accumulated SEO equity and user experience.

ccTLD redirect patterns: companies with country-specific ccTLD domains often use redirect management to route traffic appropriately. A global site at example.com with country-specific registrations at example.de, example.fr, example.co.uk may redirect each ccTLD to the corresponding localised section of the primary domain, example.de to example.com/de, example.fr to example.com/fr. Or the ccTLDs may host localised content independently. Both patterns are common, the redirect approach provides a single content infrastructure while the independent hosting approach provides stronger geographic signals.

New gTLD adoption and brand protection: as new gTLDs proliferate brand protection becomes more complex. An organisation that previously registered .com, .net, and .org versions of their name now faces hundreds of new TLDs that competitors or typosquatters could register. The practical approach is to register the highest-risk combinations, TLDs that are semantically relevant or commonly used in the industry, and redirect them to the primary domain, while accepting that comprehensive TLD coverage across hundreds of extensions is impractical.

TLD registration policies

Each TLD has its own registration policies set by the registry operator. Understanding these policies is relevant when choosing a TLD or managing a domain portfolio.

Open registration TLDs: most gTLDs including .com, .net, .org, and most new gTLDs have open registration, anyone can register any available domain name without eligibility requirements. First come first served, the first registrant of a name gets the domain.

Restricted TLDs: some TLDs require proof of eligibility. .edu requires US accreditation. .gov requires US government status. .bank requires financial institution verification. .health has healthcare-specific requirements. Restricted TLDs provide more trust for users within their domain because registrants have been verified.

Geographic requirements: some ccTLDs require local presence, a registered business address, local contact, or citizenship in the relevant country. .de requires a German contact address. .eu requires an EU address. Requirements vary by ccTLD and some have relaxed restrictions while others maintain them.

Sunrise periods for new TLDs: when new gTLDs launch they typically offer a sunrise period for trademark holders to register their marks before general availability. Organisations with registered trademarks can claim their corresponding domain in new TLDs during sunrise to prevent trademark infringement.

Registry premium domains: registry operators designate certain domain names as premium, charging higher registration and renewal fees for desirable short names or dictionary words. Premium pricing varies by registry from modestly higher to thousands of dollars annually. Brand protection registrations across TLDs may encounter premium pricing for common words.