What Is a TLD? Choose the Right Ending for Your Domain Name
Learn where a TLD appears, how generic and country-code endings differ, and which registration checks matter before choosing an extension.
- guide
A TLD, or top-level domain, is the highest named level beneath the DNS root. In example.com, .com is the TLD. The .ch suffix is another TLD. The DNS terminology standard defines the hierarchy.
For a domain buyer, the practical question is which ending fits the audience, registration rules, and recurring budget. A familiar ending can help people recognize an address. The ending does not replace a good name, a working website, or appropriate security controls.
A domain name contains several levels
Read the hypothetical address https://shop.example.com/products in separate parts. The scheme is https, the hostname is shop.example.com, and the path is /products. MDN explains these URL components.
| Component | Example | Meaning |
|---|---|---|
| TLD | .com | The highest named DNS level beneath the root |
| Second-level label | example | The label immediately beneath .com |
| Subdomain label | shop | A label beneath example.com |
| Application path | /products | A resource selected by the website |
DNS labels form a hierarchy. A path does not become a DNS label because the path appears in a web address. Our subdomain examples show how prefixes such as shop and support relate to the parent domain.
Do not assume every registrable domain contains exactly two labels. Some registration structures include additional public labels. Confirm the complete domain that the registrar offers, rather than counting dots and guessing.
The rightmost-label explanation describes the familiar written form without a trailing root dot. Technical documentation may write an absolute name as example.com.. The final dot represents the DNS root, not another commercial extension.
Generic and country-code classifications answer different questions
IANA’s Root Zone Database identifies TLD delegations and their types. The database provides a better starting point than a registrar’s marketing category.
| Classification | Examples | Buyer’s next check |
|---|---|---|
| Generic | .com, .org, .app | Registry policy and registrar support |
| Country code | .ch, .uk, .io | Local association and registry eligibility |
| Internationalized spelling | A TLD written in a non-Latin script | Exact spelling, registration policy, and application compatibility |
| Brand-associated ending | .google | Whether the registry permits the intended registration |
The descriptions can overlap. A TLD’s script describes how people write the label. The script does not replace the registry’s generic or country-code classification.
A generic TLD does not automatically mean every person can register every name. A delegated extension can have eligibility restrictions or a limited registration purpose. Read the operator’s policy before treating a name as a purchase option.
A country-code TLD also does not automatically require local citizenship. Eligibility depends on that registry’s rules. For example, our .ch registration guide explains the Swiss registry’s conditions. Do not apply one country-code registry’s conditions to another registry.
The official root list identifies extensions rather than available names
Open IANA’s Root Zone Database. Search for an extension and open the extension’s delegation record. The record identifies the TLD manager and related delegation information.
IANA’s database does not promise that yourbrand is available beneath that extension. A registrar’s search answers that separate question. Even an available search result does not resolve trademark or contractual questions.
For a wider browsing list, use our domain extensions list. The list groups examples for comparison and links back to the official source. The present article explains what those categories mean.
Keep three questions separate: Does the extension exist in the public DNS? Can the intended applicant register beneath the extension? Is the exact desired name currently available? Each question needs its own evidence.
Search engines can interpret country-code endings differently
Google describes country-code domains as a signal of a country audience. Google also lists exceptions that Google treats as generic, including .io and .ai. Google’s regional-site documentation explains the distinction.
The registry classification and Google’s search treatment answer different questions. Google’s generic treatment of .io does not turn .io into a generic TLD in IANA’s records.
Use the audience as a practical decision factor. A Swiss organization serving Swiss customers may find .ch appropriate. A product addressing several countries should evaluate whether a country association helps the product’s intended presentation.
No extension in this guide guarantees rankings. Choose an address that visitors can read and remember, then build useful content and a functioning website. Treat a promised automatic ranking boost as a claim that needs separate evidence.
You should compare the full registration terms before checkout
A domain registration grants use under a registration agreement and term. ICANN distinguishes domain registration from the other services needed to create a website. ICANN’s domain-name guidance explains the separation.
Before choosing the ending, record the following details for each candidate:
- The exact spelling and extension.
- The first registration term and price currency.
- The ordinary renewal price and renewal term.
- Any premium-name pricing conditions.
- Applicant eligibility and verification duties.
- Transfer requirements and support access.
- Included DNS services and separately billed products.
This checklist is practical buying advice. It does not imply that every registry uses the same pricing or transfer rules. Review the actual registrar agreement and registry policy for the chosen extension.
Try the complete address aloud. Ask someone to type the address after hearing the address once. Check whether a short ending creates confusion with another ending or an expected .com address. Those simple exercises can reveal a naming problem before you pay.
A clear next step turns the definition into a choice
Create a shortlist with a broad ending, a relevant country-code ending, and an appropriate descriptive ending when available. Remove options whose eligibility or renewal terms do not fit the project.
Then search the exact names with a registrar that supports the chosen extensions. Save the quoted term and renewal conditions before checkout. Arrange hosting, email, and HTTPS according to the services the project actually needs.
A TLD is one part of the address decision. Understanding the hierarchy helps you compare extensions without confusing a registration, a subdomain, and a website package.
Use Namefi's supported-extension directory to see which endings Namefi currently lists for its service. Keep IANA's root list for the broader delegation question. A listed extension does not establish the availability, eligibility, or current price of a particular name.
Sources and further reading
The DNS standard defines top level domains
The DNS standard defines top level domains, checked 2026-10-30.
IANA lists the delegated extensions
IANA lists the delegated extensions, checked 2026-10-30.
Google describes country targeting signals
Google describes country targeting signals, checked 2026-10-30.
ICANN explains domain registration
ICANN explains domain registration, checked 2026-10-30.
MDN explains URL anatomy
MDN explains URL anatomy, checked 2026-10-30.
Contributors
Aileen Wright is a student in her twenties living in New York City, where the distance between a museum wall and a library reading room is a short walk and a long afternoon. She came to name writing through art and history — the way a single portrait, coin, or manuscript margin can carry a name across centuries and change its meaning on the way.
Most weeks you can find her in Central Park with a paperback, or in the quiet of a public reading room chasing down where a name actually comes from rather than what a name-list says it means. She is also teaching herself to code, which has made her oddly precise about spelling, sorting, and the small details that decide whether a name ages well.
For Namefi she writes about the history and culture behind domain names, the stories brands carry as they rename, and the difference between a good story and a verified source.
Victor Zhou is a technology founder and standards editor focused on digital identity and trust. He founded Namefi, edits Ethereum Improvement Proposals, and previously led smart-contract architecture work at Google Labs.
His work sits at the intersection of naming, ownership, and the systems people use to establish identity online. That perspective makes him especially interested in the way names move between personal meaning, public recognition, and digital infrastructure.
For Namefi, Victor edits and writes about domains as durable digital identity: how names become ownable onchain assets, how tokenization changes custody and trust, and what naming can learn from the systems people use to establish identity online.