Domain extension meaning: gTLD, ccTLD and sTLD explained

A domain extension is the part of a web address that comes after the last dot. In "example.com", the extension is ".com". In "bbc.co.uk", the extensions are ".co.uk" (the full suffix). There are over 1,500 extensions available today, and they fall into a few well-defined categories that each behave differently for users, search engines, and registrars.

Anatomy of a domain name

A full web address breaks down like this:

https://www.example.com
  │      │   │       │
  │      │   │       └─ Extension (TLD): .com
  │      │   └─────── Second-level domain: example
  │      └─────────── Subdomain: www
  └────────────────── Protocol: https://

The extension is also called a TLD (Top-Level Domain), because it sits at the top of the domain name hierarchy managed by ICANN. Below the TLD is the second-level domain (the name you register), and below that are subdomains (optional prefixes like "www", "blog", or "shop").

ICANN (the Internet Corporation for Assigned Names and Numbers) oversees the global domain system. Each extension is operated by a specific registry, a company or organization that maintains the authoritative list of registered names under that extension. Registrars (like GoDaddy, Namecheap, or OVH) are the intermediaries through which you actually register a domain.

TLD, second-level domain, subdomain: keeping them straight

These terms are commonly confused:

• TLD: .com, .org, .fr, .dev, the extension at the right end
• Second-level domain (SLD): the name you register (example, mybrand, yourcompany)
• Subdomain: a prefix you add yourself (blog.example.com, "blog" is the subdomain)

You register the SLD plus TLD combination. Subdomains are created by you, not registered separately.

The main categories of extensions

1. gTLD: generic top-level domains

The original gTLDs were created in 1985 and are sometimes called the "Big Six":

• .com, commercial, but now used for virtually everything
• .org, originally for organizations, still strongly associated with nonprofits
• .net, originally for network infrastructure, now general use
• .edu, restricted to accredited US educational institutions
• .gov, restricted to US federal, state, and local government entities
• .mil, restricted to the US military

Of these, .com, .org, and .net are open to anyone. The others have eligibility restrictions that are strictly enforced.

2. ccTLD: country-code top-level domains

ccTLDs are two-letter extensions assigned by the ISO 3166-1 standard to countries and territories. There are about 255 of them. Examples:

• .fr = France
• .de = Germany
• .uk = United Kingdom
• .jp = Japan
• .au = Australia
• .br = Brazil

Some ccTLDs are used globally as generic extensions because of their letter combinations: .io (British Indian Ocean Territory), .co (Colombia), .ai (Anguilla), .tv (Tuvalu). Their country origin is largely irrelevant to the businesses that use them.

For the full guide on ccTLD eligibility rules and local SEO implications, see /blog/country-code-tld-guide.

3. New gTLDs: since 2013

ICANN's New gTLD Program, launched in 2012, allowed the creation of entirely new generic extensions. Over 1,200 have been delegated. They fall into several subcategories:

• Sector/niche extensions: .shop, .store, .blog, .news, .app, .dev
• Geographic extensions: .london, .paris, .nyc, .berlin
• Brand extensions: .google, .apple, .amazon (closed to the public, used internally)
• Community extensions: .sport, .music (with community governance requirements)

Most new gTLDs have limited adoption. A few (.app, .dev, .shop, .ai) have become genuinely established in their niches. For the breakdown of which ones have real adoption, see /blog/new-gtld-guide.

4. sTLD: sponsored top-level domains

Sponsored TLDs are managed by specific organizations for defined communities. They predate the new gTLD program and are not the same thing.

Examples:

• .edu, educational institutions (US), managed by Educause
• .gov. US government, managed by the General Services Administration (GSA)
• .mil. US military, managed by the Defense Information Systems Agency (DISA)
• .aero, aviation industry, managed by SITA
• .museum, museums, managed by the Museum Domain Management Association
• .int, international treaty organizations, managed by ICANN

These are not accessible to the general public. Eligibility is strictly verified by the sponsoring organization.

Summary table

Type	Examples	Open to all?	Who governs
Legacy gTLD	.com, .org, .net	Mostly yes (.edu/.gov/.mil restricted)	ICANN-accredited registries
ccTLD	.fr, .de, .uk, .jp	Varies, many have local requirements	National registries
New gTLD	.app, .shop, .store, .london	Generally yes	Private registries, ICANN oversight
sTLD	.edu, .gov, .aero, .museum	No, restricted communities	Sponsoring organizations

What the extension signals to users

Extensions aren't neutral. Users have developed associations with them over decades, and those associations affect behavior.

• .com signals general-purpose business or service. It's the default assumption for most users worldwide. When someone hears a brand name, they instinctively try the .com first.
• .org signals nonprofit, community, or cause-based organization. The association is strong enough that .org is often used by for-profit companies that want to project a mission-driven image.
• ccTLDs signal local relevance. A .de site feels more German to a German user than a .com. This is why local businesses in Europe often prefer their national ccTLD.
• .edu and .gov signal institutional authority. A link from a .edu or .gov domain carries significant weight in SEO precisely because these extensions have strict eligibility, their existence implies real institutional standing.
• New gTLDs signal niche or sector specificity. .dev tells a developer audience something about the product before the page loads. .shop says "this is e-commerce." These associations are weaker than the legacy extensions but present.

Worth knowing about .org: Many people assume only nonprofits can register .org. That's not true. .org is an open extension, anyone can register one. The association with nonprofits comes from convention and expectation, not from technical restrictions. A for-profit company running myproduct.org is perfectly legal, just unusual.

Extensions and WHOIS/RDAP: why it varies by TLD

Each TLD has its own registry with its own WHOIS and RDAP policies. This is why looking up domain information can feel inconsistent depending on what extension you're querying.

.com and .net domains go through Verisign's WHOIS/RDAP servers. .fr domains go through AFNIC's servers, with strict GDPR-compliant data policies, personal registrant information is redacted for natural persons. .eu domains have similar privacy protections. New gTLD data policies vary widely by registry.

For IT admins and developers, this means you can't assume the same data will be available for a .de lookup as for a .com lookup. The registrant name might be present on one and redacted on the other. The expiration date format differs. The contact fields vary.

Domain Sentinel normalizes these differences. When you look up a domain through Domain Sentinel, you get a consistent presentation of RDAP data regardless of which TLD you're querying, .com, .fr, .de, .app, or any of the 1,200+ new gTLDs. The underlying protocol differences are handled automatically.

The full picture

Understanding the extension taxonomy is the foundation for everything else in domain strategy, choosing the right TLD for your business, understanding ccTLD eligibility rules, evaluating new gTLDs, or managing a multi-TLD portfolio.

For the practical decision on which extension to use: /blog/how-to-choose-tld.

For new gTLDs in detail: /blog/new-gtld-guide.

For ccTLD rules and local SEO: /blog/country-code-tld-guide.

For the .com vs .io comparison: /blog/com-vs-io-domain.

Regardless of which extension you use, the lookup process (checking registration status, expiration dates, registrant information) is standardized through RDAP. Domain Sentinel runs RDAP queries for any extension, presenting the data in a consistent format across all supported TLDs.