Country code TLDs: the complete guide for businesses

A country-code TLD (ccTLD) is a two-letter domain extension assigned to a specific country or territory under the ISO 3166-1 standard. There are approximately 255 ccTLDs currently delegated, one for each recognized country and several for dependent territories. Examples: .fr (France), .de (Germany), .uk (United Kingdom), .jp (Japan), .au (Australia).

This guide covers what makes ccTLDs different from generic extensions, which ones have eligibility restrictions, how they affect local SEO, and how to manage a multi-country ccTLD portfolio without losing a domain to an overlooked expiration.

ccTLD vs gTLD: the fundamental difference

A ccTLD is assigned by the ISO 3166-1 standard to a country or territory and administered by a national registry. A gTLD is a generic extension with no geographic affiliation, administered under ICANN's root zone management. The difference in practice:

Dimension	ccTLD	gTLD
Governance	National registry, supervised by ICANN	ICANN-accredited registry operators
Eligibility	Often requires local presence or entity	Typically open to anyone
Geographic signal	Strong (tells search engines the content targets a specific country)	None (new gTLDs) or weak
Examples	.fr, .de, .uk, .jp, .au	.com, .org, .app, .shop

Note: some ccTLDs have become widely used as generic extensions because they have memorable two-letter combinations or relevant meanings in English, .io (British Indian Ocean Territory), .co (Colombia), .ai (Anguilla), .tv (Tuvalu). Their registries operate commercially with no geographic restrictions. For more on these, see /blog/new-gtld-guide.

ccTLDs used as generic extensions (.io, .ai, .co)

These extensions are technically ccTLDs but function as generic extensions in practice. The country behind the extension has no bearing on who can register or what can be published. The risk: the registry is often a private company with a contractual relationship to a small territory government, which adds a layer of instability compared to a registry like Verisign (.com) or AFNIC (.fr).

Eligibility restrictions: who can register what

This is the section most IT admins and domain managers actually need. Eligibility rules vary dramatically by extension.

Extension	Country	Requirement	Workaround possible?
.co	Colombia	None, open to all	N/A
.io	BIOT	None, open to all	N/A
.fr	France	EU address required (AFNIC)	Yes, via local administrative contact
.de	Germany	Administrative contact in Germany required	Yes, via registrar-provided admin handle
.eu	EU	Must be EU resident or entity	No effective workaround
.uk	UK	UK address required	Yes, via registrar proxy services
.au	Australia	Australian Business Number (ABN) required	No, must have actual ABN
.cn	China	Registered Chinese entity required	No
.ru	Russia	Russian entity required	No
.jp	Japan	Japanese entity or local representative required	Yes, via designated representative

For the .fr specifically: AFNIC (the French registry) requires that the domain holder has an address within the European Union. Non-EU entities can register through a local administrative contact provided by most major registrars (OVH, Gandi, Namecheap all handle this). The process adds a small layer of setup but isn't a blocker.

For .au: the requirement for an Australian Business Number is genuine. You cannot circumvent it with a proxy. If you need a .au for Australian market presence, you need to establish an Australian entity or work through a local partner who holds the domain on your behalf under a proper legal arrangement.

How to verify ccTLD rules for a specific extension

The authoritative source is the IANA root zone database (iana.org/domains/root/db), each entry links to the registry's contact information. The registry website usually publishes its eligibility policy. For obscure ccTLDs, the ICANN WHOIS database sometimes shows the registry's homepage URL.

ccTLDs for local SEO: what actually works

A ccTLD sends a stronger geographic signal to Google than geotargeting a .com in Google Search Console. This is well established. A .de domain is understood by Google as serving a German audience before any configuration is done. With a .com, you have to explicitly set up geotargeting in Search Console, and the signal is weaker.

The practical effect: for searches with local intent in Germany ("Versicherung Berlin", "Fahrrad kaufen"), a .de will tend to outrank a geotargeted .com, assuming similar content quality and link profiles. The gap is smaller in less competitive niches but still present.

ccTLD and Google Search Console: how geotargeting works

For a ccTLD, Google assigns the geographic target automatically. You can override this in Search Console, but the ccTLD signal overrides most manual configurations. For a gTLD like .com, you set the geographic target in Search Console per site, and Google treats it as a signal, not a determinant.

When .com is still preferable even locally

Two scenarios where .com beats the local ccTLD:

First, if your business operates in multiple countries and you cannot afford separate sites per country, .com with localized subfolders (acme.com/de/, acme.com/fr/) is more manageable and has acceptable SEO performance for international sites.

Second, if the ccTLD eligibility requirements are a significant operational burden for your structure. There's no SEO benefit from a ccTLD that expires because your administrative contact setup lapsed.

Multi-country strategy: managing a ccTLD portfolio

For businesses operating across several countries, three approaches exist:

Approach	Advantages	Disadvantages	Recommended when
ccTLD per country (acme.fr, acme.de, acme.es)	Strong local SEO signal in each market	High management complexity, multiple registries	Business is primarily local in each market
Subfolder (.com/fr/, .com/de/)	Centralized management, single domain to renew	Weaker geographic signal than ccTLD	International product, moderate local SEO needs
Subdomain (fr.acme.com, de.acme.com)	Easy server configuration	Less recommended by Google, weaker than subfolder	Legacy setups, specific technical constraints

The biggest operational risk with a ccTLD portfolio is fragmented expiration dates. A business with 15 ccTLDs across 15 countries has domains expiring at different times, registered through different registrars (some of which don't send renewal reminders in your language), under different billing cycles. One missed renewal can mean losing a domain that took years to build authority on.

How Domain Sentinel handles a multi-registry ccTLD portfolio

Domain Sentinel queries RDAP data across all ccTLD registries and normalizes the expiration dates into a single dashboard. You set alert thresholds (60 days, 30 days, 7 days before expiration) and receive notifications regardless of which registry holds the domain. This is the main operational risk management tool for anyone running more than five or six ccTLDs.

Key ccTLDs by region

Extension	Country	Notable features
.de	Germany	DENIC registry, admin contact in DE required, 17M+ registered
.uk	United Kingdom	Nominet registry, no .uk direct until 2019, now growing
.fr	France	AFNIC, EU address required, strong for local SEO
.nl	Netherlands	SIDN, very open registration, 6M+ registered
.es	Spain	RED.ES, 2M+ registered, Spanish entity preferred
.it	Italy	Registry.it, Italian residence or EU company required
.pl	Poland	NASK, Polish presence required or local contact
.ch	Switzerland	SWITCH, address in CH required
.us	United States	US nexus required, underused compared to .com
.ca	Canada	CIRA, Canadian Presence Requirement
.mx	Mexico	NIC México, open but local registrar often used
.br	Brazil	Registro.br, Brazilian entity required, strictly enforced
.au	Australia	auDA, ABN required
.jp	Japan	JPRS, Japanese entity or local representative
.cn	China	CNNIC, registered Chinese entity required
.in	India	NIXI, open registration, no residency required
.kr	South Korea	KISA, Korean entity or local representative
.sg	Singapore	SGNIC, Singapore company or individual required
.za	South Africa	ZADNA, South African entity required
.ng	Nigeria	NiRA, open registration
.ae	UAE	TRA, UAE entity or local registrar sponsor required

The practical recommendation

If your audience is primarily in one country and you can satisfy the eligibility requirements, the local ccTLD is usually the better choice for local SEO. The signal is stronger, the setup is simpler for geotargeting, and it often aligns with user expectations (a .de site feels more local to German users than a .com).

If you manage several ccTLDs, the main risk to control is expiration. Domain Sentinel centralizes expiration monitoring across all your registries and sends unified alerts before any domain lapses.