ccTLD cc codes explained: country-code domain extensions and local SEO

What a ccTLD cc code is and how country codes map to countries

A ccTLD, or country-code top-level domain, is the two-letter extension after the final dot that ties a domain to a specific country, sovereign state, or dependent territory. In example.co.uk the country code is .uk.

The defining rule is simple. Every ASCII ccTLD is exactly two letters, and every two-letter top-level domain is a ccTLD.

That two-letter string is not chosen by a registry. It is drawn from the ISO 3166-1 alpha-2 list, the same standard that gives the United Kingdom “GB” and Germany “DE”.

The two-letter form separates ccTLDs from generic extensions at a glance:

• Country-code ccTLDs: two letters tied to a territory, like .uk, .de, .fr, and .jp.
• Generic gTLDs: three or more letters, open to anyone, like .com, .net, and .org.
• The exceptions that prove the rule: .uk and .eu, which sit beside the ISO codes GB and the EU region for historical and regional reasons.

The two-letter code is borrowed, not assigned by the domain industry.

The reason ccTLDs feel consistent worldwide is that the namespace did not invent the codes. It reused a list that already existed for shipping, banking, and customs.

That borrowing is deliberate. It lets the country code stay neutral, because the decision about which territories count as countries sits with a standards body, not with a domain registry.

The distinction the glossaries blur is between the code and the operator that runs it. The string is .uk; the operator is Nominet, which sets the registration policy, the price, and the renewal terms for that country.

Reading the operator alongside the code is the first read a serious country-market acquisition runs, and it is what the lookup tool below makes fast.

Searchable ccTLD lookup: code, country, registry, and restriction

The lookup below holds 67 ccTLDs, each with its country, its real registry operator, whether registration is open or restricted, and a short geo or resale note, filterable by restriction type and searchable by code or country. Type a code or a country name, or filter to open, restricted, or generic-use extensions.

Every row draws its country and operator from the IANA Root Zone Database and the named registries. The generic-use flag follows Google’s documented list. No value scores, no invented facts.

The tool runs entirely in your browser. With scripting off, the full table still renders as static HTML below.

How IANA assigns ccTLDs through ISO 3166-1 and RFC 1591

IANA assigns a ccTLD by taking the two-letter code from the ISO 3166-1 alpha-2 list and delegating it to a registry that agrees to act as a trustee for that country's Internet community. The framework dates to RFC 1591, drafted by Jon Postel in 1994.

The design choice at the centre is neutrality. IANA states it is "not in the business of deciding what is and what is not a country," so it leans on the ISO list maintained by a separate standards body.

The assignment runs in a fixed order:

• Eligibility: a string qualifies when it is an ISO 3166-1 alpha-2 code, so .de exists because "DE" is on the list.
• Delegation: IANA delegates the code to a manager that demonstrates it can serve the local Internet community fairly.
• Trustee duty: the manager runs the extension as a trustee, not an owner, on behalf of the national and global communities.

The ISO list does the deciding, which keeps the assignment apolitical.

The settled point about ccTLD eligibility is that the domain system delegates the hardest decision. Whether a territory is a country is answered by the ISO 3166 Maintenance Agency, not by IANA or any registry.

That separation is the reason the namespace stays stable when borders or recognition shift. The code follows the list, and the list follows a transparent, neutral procedure.

Internationalised ccTLDs, also written internationalized, are the non-Latin-script country strings. They are delegated through the ccTLD Fast-Track process and stay valid only while the country remains on the ISO 3166-1 standard.

Delegation is not permanent ownership. The transferring or redelegation of a ccTLD follows the same trustee obligations, so a registry's management of the string answers to a public-interest duty instead of a private title.

The wider governance picture, from ICANN coordination down to the registry contract, is set out in the sibling guide What is a TLD? The top-level domain explained, from the dot to the governance behind it.

ccTLD eligibility: open, restricted, and local-presence rules

ccTLD eligibility splits into open extensions anyone can register and restricted ones that demand a local presence, a national address, or a documented connection to the country. The trustee duty is why the rules differ so sharply by registry.

The split is the single key practical fact a buyer reads before choosing a country-code name. It decides whether the extension is reachable at all.

The three working categories map directly onto the lookup tool's filters:

The eligibility rule is a trust signal, not just a hurdle.

The restriction the gate imposes doubles as a trust marker. When .ca demands Canadian presence, a .ca site carries an implicit verification that an open extension does not.

For a domestic business, that gate is a feature. The harder the extension is to register from outside the country, the stronger the local credibility it confers on the registrant who clears it.

For an acquirer, the gate is also a logistics fact. A restricted ccTLD can need a local contact, a registered entity, or a trustee service to hold and transfer cleanly, which is part of the diligence on any country-market name.

Confirm the registry's current eligibility rule before assuming a country code is reachable, because the gate varies by registry and the registry can revise it.

How a ccTLD geo-targets and the local-SEO mechanics behind it

A country-code extension acts as a strong, automatic geo-targeting signal: Google associates a .de with Germany by default, and that country setting cannot be changed in Search Console. The signal is the ccTLD's defining SEO property.

The mechanic is documented. Google states a ccTLD tied to a country "provides a strong signal" for that location, with no manual setup needed.

The ccTLD is one way of using country-specific URLs to tell Google a market. The alternative is qualifying a single domain with localized country versions, each addressed by hreflang, which a cross-border brand reaches for when one country lock will not serve every market.

The ccTLD is one geo signal among the geo signals Google reads, and the others matter when a site spans markets:

• hreflang annotations: tell Google which language and region version to serve, the main tool for a cross-border site.
• Server and IP location: a weaker, complementary indicator of where a site is hosted.
• Local addresses, phone numbers, language, and currency: on-page signals that reinforce the country focus.
• Links from other local sites: inbound links from the target market that corroborate local relevance.

The geo signal helps at home and constrains reach abroad by design.

The geo-targeting strength is a feature with a built-in cost. When Google treats .de as a strong indicator a site serves Germany, the site gains local relevance and gives up implied global reach.

For a national retailer or a regional service business, that trade is worth taking, and the ccTLD is the right tool. For a cross-border brand, it forces a structural choice between one country domain per market and a single gTLD with hreflang.

The constraint is also why a ccTLD rarely competes head-to-head outside its country. A .fr site starts from a colder position for a query outside France, even with identical content.

How the extension choice feeds direct ranking versus indirect trust is set out in the sibling guide Does your domain extension affect SEO? The data, the myths, and the aged-domain nuance.

Generic-used ccTLDs versus country-restricted ones

A documented set of ccTLDs is read globally instead of locally, because Google treats them as generic and the market adopted them as brand extensions instead of country flags. The list is published, not folklore.

Google names the geotargetable ccTLDs it treats as generic, so they can be geotargeted manually instead of locked to a country. The set includes .io, .ai, .co, .me, .tv, .cc, .fm, .la, and .ws.

This commercial usage is what separates them. The market repurposed these country strings for global vanity branding, so .io reads as a tech extension and .tv as a video one, an unconventional usage their ISO origin never intended.

The practical split between the two reads runs along three lines:

The read depends on the specific code, not on the two-letter form.

Treating all ccTLDs as country flags is the error the glossaries make. A .de is a country signal; a .io is a global brand extension, even though both are two letters from the same ISO list.

The working rule is to check whether a given code sits on the generic-treated list before assuming geo behaviour. The same two-letter form can mean "for one country" or "for the world."

For a global product on a generic-used ccTLD like .io or .ai, the extension behaves like a gTLD on the ranking axis and carries its own premium resale market. The geo penalty that constrains a true country ccTLD does not apply.

The family-level contrast between country codes and generic extensions, on eligibility and aftermarket value, is mapped in the broader Domain extensions list: Every TLD type and what each one signals.

Why an aged ccTLD carries local authority and resale value

On the aftermarket an aged ccTLD carries inherited local authority, because a country-code name with clean history and a relevant backlink profile starts from a warmer position in its own market than a fresh registration. This is the lens the registrar lists omit.

The investor read inverts the registration question. A fresh ccTLD weighs the geo fit and the eligibility gate. An acquisition weighs inherited equity, local trust, and how fast the name converts in its home market.

Three facts drive aftermarket value on a country-code name:

The extension prices the local liquidity, and the history prices the equity.

The distinction that matters on a country-market acquisition is between equity and liquidity. The inherited backlink profile and topical history decide the SEO value; the extension decides how the name converts in its market.

An aged ccTLD with a clean, relevant in-country profile combines both: the equity that carries the ranking and the geo signal that anchors it to the target market. A new registration on the same extension carries the geo signal and none of the inherited authority.

The condition on inherited equity is relevance and cleanness, not the country code. A profile concentrated in relevant, clean local sources transfers authority forward; an engineered profile discounts the name on .de as readily as on any extension.

How that inherited value is read and scored runs through the metric guide What is a good Domain Authority score, and the way an acquired domain's age carries forward is covered in Does domain age still matter for SEO in 2026.

How a screened catalogue reads the ccTLD inside a country market

The whole guide resolves to one operational point: the country code is one signal, and the eligibility rule, the geo behaviour, and the inherited local history are what decide value. The definition, the assignment chain, the geo mechanics, and the lookup all point the same way.

SEO Domains reads a country-code name exactly that way at intake. The curated catalogue screens each aged domain in a fixed order:

• Its inherited backlink profile, read for relevance and cleanness in the target market.
• Its topical history, read against the buyer's intended use and country.
• Its abuse and trademark exposure, surfaced before acquisition.
• The extension and its eligibility rule last, read as a geo-and-liquidity modifier on top of that screen.

Domain Authority, Domain Rating, Trust Flow, and Citation Flow are reported alongside the inheritance read, so a buyer sources a country-code name selected on the local history that decides the SEO, with the extension placed as the geo modifier it is.

The catalogue reads inherited local equity before the country code.

The discipline SEO Domains applies is to invert the order the registrar lists encode. A raw country list prices a name on its geo signal and leaves the local history unread.

The catalogue reverses that. It reads the inherited in-country backlink profile for relevance and cleanness, reads the topical history against the buyer's market, reads the abuse and trademark exposure, and only then reads the extension and its eligibility rule as the geo-and-liquidity modifier they are.

An aged domain on a country-code extension combines the inherited local SEO equity that carries the ranking with the geo signal that anchors it to the market. ICANN-accredited transfer applies to every acquisition, and the registry's own eligibility rule governs who can hold the name.

A buyer who reads a country code by its rule and its local history, not by the flag alone, is the buyer best served by inventory screened on the history that is the larger lever.

A screened catalogue raises confidence in the local history, and it guarantees no outcome.

The honest takeaway is two-sided. A geo signal sold as inherited authority, a generic-used ccTLD assumed to geo-target, an eligibility gate discovered at transfer, and a country lock pitched for a global brand are real ways a country-code decision goes wrong.

They concentrate in unscreened pools where a name reaches a buyer priced on its flag with its local history unread.

A screened catalogue does not write the content, earn the new local links, or run the conversion the inherited equity rewards. It does not provide financial, investment, or legal advice, and it promises no ranking or sale outcome on any name or extension.

What it does is read the inherited in-country equity, the topical history, the abuse exposure, and the eligibility rule that decide the outcome, and place the country code where this guide places it, as one signal on top of the asset.

A reader who finishes this guide is equipped to stop reading the flag in isolation and start reading the country-code domain.