--- id: "tld" kind: "glossary-term" title: "TLD" language: "en" category: "TLD types and programs" updated: "2026-10-10T10:28:55Z" canonical: "https://tldlog.com/glossary/tld/" translations: es: "https://tldlog.com/es/glosario/tld/" de: "https://tldlog.com/de/glossar/tld/" fr: "https://tldlog.com/fr/glossaire/tld/" it: "https://tldlog.com/it/glossario/tld/" pt-BR: "https://tldlog.com/pt/glossario/tld/" ru: "https://tldlog.com/ru/glossariy/tld/" zh-Hans: "https://tldlog.com/zh/cihui/tld/" --- # TLD top-level domain The last label of a domain name, after the final dot, such as .com, .de or .app. TLDs sit directly below the root zone. The two main types are country-code TLDs and generic TLDs. Each is run by a registry that sets rules within any contract or local framework. A top-level domain, or TLD, is the last part of a domain name, after the final dot. In `www.example.com` the TLD is .com, and in example.org it is .org. Every domain name on the internet sits under one TLD. ## What a top-level domain is The DNS is organized like a tree. At the top is the root zone, and one level below it are the TLDs. The root zone is mainly a list of TLDs and the name servers that answer for each of them. For the DNS itself, a TLD is an ordinary zone. RFC 9499, the technical standard on DNS terms, says there is "nothing special" about TLDs from the point of view of the DNS. The split into country code and generic TLDs is a matter of policy, not technology. In March 1994, RFC 1591 listed seven generic TLDs (.edu, .com, .net, .org, .gov, .mil and .int) plus the two-letter country codes, and said that other TLDs were "extremely unlikely". Since June 1999, RFC 2606 has reserved .test, .example, .invalid and .localhost so that they never become real TLDs. Names under .example are meant for documentation. ## The main families: generic, country code, sponsored, brand and infrastructure IANA's database gives each TLD a type: generic, country-code, sponsored, generic-restricted, infrastructure or test. - **Country code (ccTLD).** Mainly a two-letter code from the ISO 3166-1 list of country codes, such as .es or .de, plus IDN ccTLDs in non-Latin scripts. IANA follows that list and does not decide what counts as a country. There are a few exceptions, such as .eu (a code exceptionally reserved for the European Union) and .uk (kept although the ISO code for the United Kingdom is GB). - **Generic (gTLD).** A string becomes a gTLD after it passes ICANN's evaluation and signs a contract with ICANN, as .com, .org and .app did. Place names such as .madrid and .barcelona are also generic, run by the Comunidad de Madrid and the Municipi de Barcelona. Country and territory names are not approved as gTLDs. - **Sponsored (sTLD).** As of October 2026, IANA lists 14, including .aero, .cat, .edu, .gov, .int and .museum. - **Brand (.brand).** Not an IANA type: .bmw, for example, appears as generic. ".Brand" is a status in the ICANN contract. The string must match a registered trademark the operator owns and uses, and only the operator, its affiliates or its trademark licensees may hold names. - **Infrastructure.** Only .arpa, used for technical needs such as in-addr.arpa and ip6.arpa, which map numeric internet addresses back to names. IANA runs it under the guidance of the Internet Architecture Board (IAB). ## Open versus restricted TLDs In an open TLD, anyone can register a name. In a restricted TLD, only people or organizations that meet set rules can register. Those rules can come from three places, and in each case the registry enforces them: - **Registry policy.** A gTLD registry may set non-discriminatory criteria that are reasonably related to how the TLD works. - **The ICANN contract.** A community TLD must have registration policies that cover, at a minimum, who may register and which names they may choose. - **Law.** Regulation (EU) 2019/517 opens .eu to EU citizens, EU residents and organizations established in the EU. The registry may revoke a name whose holder does not meet these criteria. A ccTLD can also be open in practice. Since 2005, Spain's national plan allows any person or entity with interests in or ties to Spain to register under .es, and these ideas are read broadly. A generic word cannot be closed to a single owner, and as of October 2026 ICANN will not approve "closed generic" applications until it has an approved way to judge whether they serve the public interest. A .brand is closed by design, because its string is a trademark, not a generic word. ## Who runs a TLD and who sets its rules Every delegated TLD has a manager listed by IANA. In industry terms, this organization runs the registry and decides, within its rules, who may register names and on what terms. Requests to add or change a TLD in the root zone go through IANA. The rules differ by family: - **gTLDs.** The registry signs a Registry Agreement with ICANN. It must follow ICANN consensus policies, developed mainly in the GNSO, and in most cases sell names only through ICANN-accredited registrars. - **ccTLDs.** ICANN's Bylaws limit its policy role on second-level registrations to gTLDs. The ccNSO develops global policies for ccTLDs, but few of them bind its members, so most rules are local. For example, .es is managed by Red.es under a Spanish ministerial order. When a ccTLD is delegated or transferred, the government concerned is consulted for support or non-objection. ## How to choose a TLD for a project There is no single right answer, but some questions can be checked: 1. **Eligibility.** Can the registrant register in the TLD at all, and are the rules set by ICANN policies or by local law? A company with ties to Spain but no establishment in the EU may meet the .es rule but not the .eu criteria. Brand and community TLDs are not open to everyone. 2. **Audience.** A country code stands for a country or territory. Rules change, so check the registry's current policy, and ask a lawyer when the answer depends on a specific situation. ## How many TLDs exist and how new ones are added As of October 2026, IANA's Root Zone Database lists about 1,400 TLDs with a manager. This counts database entries, not the live root zone. A new ccTLD usually follows a new code in the ISO 3166-1 list, through a delegation request with government consultation. New gTLDs come through ICANN application rounds. As of October 2026, in the 2026 Round: - Applications were accepted from 30 April to 12 August 2026, with an evaluation fee of USD 227,000 per application for most applicants. - ICANN's snapshot of 7 October 2026 showed 1,615 applications, including 333 brand, 16 community-based and 15 self-identified geographic applications. - String Confirmation Day is 17 November 2026, and the community input and objections period runs from that day to 16 March 2027. A prioritization draw follows in 2027. A TLD that passes evaluation and contracting is then delegated: it is added to the root zone and starts to work. ## Sources - [RFC 9499: DNS Terminology](https://www.rfc-editor.org/rfc/rfc9499.txt) - [Root Zone Database](https://www.iana.org/domains/root/db) - [Registry Agreement (2026 base Registry Agreement)](https://itp.cdn.icann.org/en/files/registry-agreements/base-registry-agreement-12-03-2026-en.pdf) - [ICANN Reveals 2026 Round Applications for New Generic Top-Level Domains](https://www.icann.org/en/announcements/details/icann-reveals-2026-round-applications-for-new-generic-top-level-domains-07-10-2026-en) - [Regulation (EU) 2019/517 on the implementation and functioning of the .eu top-level domain name](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32019R0517) ## related terms - [gTLD](https://tldlog.com/glossary/gtld/) - [ccTLD](https://tldlog.com/glossary/cctld/) - [root zone](https://tldlog.com/glossary/root-zone/) - [registry](https://tldlog.com/glossary/registry/)