Before Registering a Country-Code Domain
ccTLDs can be great for local trust — but they come with rules you need to know.
The golden rule: every ccTLD is different
Unlike gTLDs (which follow ICANN's standardised contracts), each ccTLD is governed by its national registry under local law. Policies vary wildly.
Eligibility / nexus requirements
Many ccTLDs require a connection to the country:
| Requirement | Examples | What you need |
|---|---|---|
| Local administrative contact | .fr, .eu, .ca | Name + address in the country (can use a trustee service). |
| Local company registration | .de, .jp, .br | Registered entity in that country. |
| Trademark in the country | .cn, .kr | Valid national trademark registration. |
| Citizenship / residency | .us, .sg | Proof of citizenship or permanent residency. |
| No restriction (open) | .ai, .io, .co, .me, .tv | Anyone can register. |
Always check the official registry website (linked from our TLD detail pages) for current requirements.
Transfer & ownership rules
- Transfers may not work like gTLDs — some ccTLDs don't support EPP transfers; you may need to re-register.
- Registrant changes can be restricted — changing the legal owner may require the same eligibility proof as a new registration.
- Dispute resolution — not all ccTLDs use UDRP. Some have local courts or arbitration (e.g.
.ukuses Nominet DRS).
Pricing & renewal surprises
- No ICANN price caps — registries can raise wholesale prices with less notice.
- Multi-year limits — some ccTLDs only allow 1-year registrations (e.g.
.ukhistorically, now 1–10 years). - Currency — you may pay in local currency (EUR, GBP, JPY, etc.).
Geopolitical risk
ccTLDs are tied to sovereign territory. If a country ceases to exist, changes borders, or loses internet connectivity, its ccTLD may be retired or transferred.
Recent examples:
.io— sovereignty dispute over the Chagos Archipelago (UK/Mauritius) created uncertainty 2021–2024..su(Soviet Union) — still exists decades after the USSR dissolved..yu(Yugoslavia) — retired 2010, replaced by.rs,.me, etc.
For critical infrastructure, prefer gTLDs or stable ccTLDs with clear governance.
Technical gotchas
- DNSSEC — some ccTLDs require or strongly encourage DNSSEC; others don't support it.
- Name server requirements — some registries require authoritative NS in-country (rare now, but check).
- IDN support — many ccTLDs support IDN second-level labels; policies vary.
Checklist before you register
- ☐ Read the registry's registration policy (link on our TLD detail page).
- ☐ Confirm you meet eligibility (or have a trustee service).
- ☐ Check transfer/ownership change rules.
- ☐ Compare 5-year total cost (renewal × 5 + any fees).
- ☐ Verify DNSSEC and name server requirements.
- ☐ Consider geopolitical stability for long-term projects.
- ☐ Register defensive variants in other TLDs.