What Is a Top-Level Domain? The Part After the Last Dot

A top-level domain is everything that follows the final dot in a domain name. In example.com the TLD is com. There are roughly 1,500 of them, they are grouped into a handful of categories with meaningfully different rules, and the practical question for most people is which one to register, not what the acronym stands for.

The definition takes one line. What is worth more space is how TLDs sit in the DNS hierarchy, why the choice affects things you would not expect, and what actually matters when picking one.

Table of contents

• Where the TLD sits in a domain name
• The categories, and their different rules
• What the TLD does in a DNS lookup
• Choosing one
• How this fits the rest of the stack
• FAQ

Where the TLD sits in a domain name

Domain names are hierarchical and read right to left, from most general to most specific.

blog.example.co.uk
|    |       |  |
|    |       |  +-- TLD (top-level domain)
|    |       +----- second-level, here part of the effective suffix
|    +------------- the registrable domain
+------------------ subdomain

Above all of it sits the root zone, written as a single trailing dot:
blog.example.co.uk.

The root zone is the top of the hierarchy and it delegates each TLD to an organisation that operates its registry. ICANN has authority over the namespace as a whole and delegates the running of individual TLDs, so com is operated by one company, uk by another, and so on.

Something people get wrong: co.uk is not a TLD. The TLD is uk, and co.uk is a second-level domain within it that the registry uses to organise registrations. The same applies to com.au and co.jp.

What matters practically is the boundary at which a name becomes registrable, which is not always at the TLD. That boundary is defined by the Public Suffix List, a maintained list browsers use to decide where cookies can be set. Without it, a site at one co.uk domain could set a cookie for all of co.uk, which would be a serious problem.

The categories, and their different rules

Generic TLDs, or gTLDs, are the original open set plus everything added since: com, net, org, info, biz, plus the several hundred newer ones such as app, dev, shop, and blog. Mostly open to anyone.

Country-code TLDs are two letters assigned to a country or territory: uk, de, fr, jp, ca. Each is run under that country’s rules, and those differ considerably. Some require local presence or a local address, some publish registrant details regardless of privacy services, and some have their own dispute processes rather than the standard one.

Sponsored TLDs are restricted to a defined community with eligibility verified: edu for accredited US educational institutions, gov for US government, mil, int, and a handful of others. You cannot simply buy one, which is precisely why they carry weight.

Brand TLDs are operated by a single company for its own use. They exist and are not available to you.

• Some newer TLDs have technical properties worth knowing. The app and dev TLDs are on the HSTS preload list at the registry level, so browsers refuse to load them over plain HTTP. Use one and HTTPS is not optional, which is a genuine security feature and an occasional surprise during local development.
• Some carry poor reputation. A few cheap TLDs are heavily used for spam and phishing, and mail filters treat them accordingly. A domain on one of those can find its email quietly delivered to spam regardless of correct authentication.
• Pricing on newer TLDs varies enormously, and renewal is often far higher than registration. Check the renewal price, not the first-year offer.

What the TLD does in a DNS lookup

Understanding the resolution path explains why the TLD is more than a label.

When a resolver has nothing cached, it asks a root server for the address of a name. The root server does not know it, and replies with the nameservers for the relevant TLD. The resolver asks those, which reply with the nameservers for the specific domain. The resolver asks those, and finally gets the record it wanted.

# Watch the delegation happen, step by step.
dig +trace example.com

# Ask the TLD's nameservers directly.
dig NS com

# Who runs a given TLD?
whois -h whois.iana.org .app

The +trace output is the clearest illustration of the hierarchy available, and it is worth running once if the structure has never felt concrete.

The practical implication is that TLD nameservers are infrastructure your domain depends on. They are extremely reliable, and the rare occasions when a TLD’s nameservers have problems take every domain under that TLD with them, which is a form of concentration risk you cannot mitigate by choosing a good registrar.

Choosing one

The considerations that actually matter, in order.

1. Take com if it is available and affordable. It remains the default assumption, people type it automatically, and it needs no explanation. This is not exciting advice and it is correct.
2. Take your country code if your business is local. A uk or de domain signals local presence to local customers and often performs better in local search.
3. Take a relevant newer TLD if com is gone and the alternative is a compromised name. A short memorable name on a good newer TLD beats a long hyphenated com.
4. Check the renewal price before registering, since introductory pricing on newer TLDs is often a fraction of the recurring cost.
5. Check for trademark conflicts before committing, because building a brand on a name someone else has registered as a mark ends badly.
6. Avoid TLDs with spam reputation if you will send email from the domain, and test deliverability early if you are unsure.

On the question that always comes up: TLD choice is not a ranking factor in itself, with the exception that country-code TLDs are a signal for that country’s local results. A site on a newer TLD is not handicapped. What matters is that people trust the name enough to click it.

The other frequent question, whether to defensively register the same name across many TLDs, is answered by proportion. The com, your country code, and anything customers would plausibly guess. Beyond that the returns fall away quickly and the list has no end.

How this fits the rest of the stack

Once the name is chosen the work is pointing it somewhere and keeping the certificate valid, which is where most of the ongoing friction with domains actually lives. Custom domains and certificates are handled as part of the platform on RunxBuild for static sites and services alike, and the RunxBuild hosting calculator shows what the site behind the domain costs as separate line items.

Useful related references:

• What Is a .link Domain, and When Does It Fit a Project?
• What Is a Parked Domain? And Why Yours Might Be a Liability
• Multi-Domain SSL: SAN Certificates, Wildcards, and What to Use
• Custom domains and certificates on RunxBuild

FAQ

What is a top-level domain?

Everything after the final dot in a domain name, such as com in example.com. It is the first level of delegation below the DNS root, and ICANN delegates each one to an organisation that operates its registry.

Is .co.uk a top-level domain?

No. The TLD is uk, and co.uk is a second-level domain the UK registry uses to organise registrations. The same pattern applies to com.au and co.jp.

Does the TLD affect SEO?

Not directly, with one exception: country-code TLDs act as a geographic signal for that country’s local results. Newer TLDs are not penalised, though some carry spam reputation that affects email deliverability rather than ranking.

How many top-level domains are there?

Roughly 1,500, comprising the original generic set, several hundred newer generic TLDs, around 300 country codes, and a set of restricted sponsored and brand TLDs.

Which TLD should I choose?

com if it is available, or your country code if the business is local. If both are gone, a short memorable name on a relevant newer TLD beats a long hyphenated com. Check the renewal price rather than the introductory one.