A ccTLD (country code top-level domain) is a two-letter top-level domain assigned to a country or territory, such as .de for Germany, .jp for Japan or .br for Brazil. In the domain name system, ccTLDs form one of the two large families of top-level domains, alongside generic top-level domains (gTLDs) such as .com, .org or newer endings like .shop.
Among domain names, a ccTLD signals a national or regional connection, and each one is run by a designated registry operator that sets its own rules for who may register, how disputes are resolved and what data is published. This local control is the main difference from gTLDs, which follow common contractual policies.
How country code domains are defined and delegated
ccTLD codes follow the ISO 3166-1 alpha-2 list of country and territory codes. The DNS root does not decide what counts as a country; it relies on that list, which keeps the root operator out of political judgments. When a code is added to the list, a ccTLD can be delegated; when a country ceases to exist, its ccTLD is eventually retired after a transition period.
Delegation is handled through the IANA functions, which record the ccTLD manager and the authoritative name servers in the root zone. The manager is typically a national nonprofit, a university network, a government agency or a contracted company. A notable exception to the ISO rule is .uk, used instead of the official code GB for historical reasons, and .eu, which is based on an exceptionally reserved code.
Internationalized ccTLDs also exist in non-Latin scripts, such as the Cyrillic domain for Russia or Chinese-script domains, encoded in the DNS with Punycode under the xn-- prefix. They are approved through a separate fast-track process.
Operationally, a ccTLD works like any other top-level domain. The registry runs the authoritative name servers for the zone and keeps the database of registered names, while accredited registrars sell names to the public, often through the EPP provisioning protocol. Some smaller ccTLDs still accept registrations directly or through a single local agent.
Types of ccTLD registration policies
Each registry decides who may register and under which conditions. Policies range from completely open to strictly local, and they shape how a ccTLD is perceived and used.
| Policy model | Typical requirement | Effect on use |
|---|---|---|
| Open | Anyone worldwide may register | Wide adoption, sometimes outside the country |
| Local presence | Resident, company or local agent | Strong national association |
| Regional eligibility | Residence within a group of countries | Shared regional identity |
| Restricted or sponsored | Specific institutions only | High trust, limited registrations |
| Second-level structure | Registration under categories such as .co.uk or .com.au | Category signals type of entity |
Some ccTLDs are popular for reasons unrelated to geography. Endings such as .io, .ai, .tv and .me are marketed globally because the letters suggest a word or industry. Search engines generally treat a defined list of such codes as generic for geotargeting, but the registry rules still remain those of the territory.
ccTLD compared with other domain categories
The difference between ccTLDs and gTLDs lies mainly in governance and policy, not in DNS mechanics. Both are delegated from the root zone and resolve in exactly the same way.
| Aspect | ccTLD | gTLD |
|---|---|---|
| Format | Two letters from ISO 3166-1 | Three or more characters |
| Policy authority | Local registry and national rules | Contracts with the global coordinating body |
| Dispute resolution | Registry-specific procedure | Uniform policy for most gTLDs |
| Registration data | Local privacy rules apply | Common rules, published through RDAP |
| Typical signal | National or regional market | Global or thematic |
| Examples | .de, .fr, .ca, .sk | .com, .net, .org, .app |
Registration data access also differs. Many ccTLDs run their own WHOIS or RDAP services with national privacy rules, so the amount of published contact information varies considerably from one ccTLD to another.
Choosing a ccTLD for a website
A ccTLD is a strong geographic signal to users and search engines. It is usually the best choice when a business serves mainly one country, and less suitable when the audience is international. The decision table summarizes common scenarios.
| Situation | Recommended choice | Reason |
|---|---|---|
| Business serving one country | That country’s ccTLD | Local trust and geotargeting |
| International brand with local markets | gTLD with country subfolders, or ccTLD per market | Balance of consolidation and local signal |
| Startup using a word-like code | Popular open ccTLD such as .io | Short, available names |
| Public institution | Restricted national second level | Official recognition |
| Uncertain eligibility | Verify registry rules first | Risk of suspension |
Risks and common misunderstandings
The biggest risk is that a ccTLD depends on the policies and stability of its territory. A registry may change eligibility rules, raise prices or, in rare cases, face changes to the territory itself. Discussions about the future of .io after the announced change in sovereignty over the Chagos Archipelago illustrate this long-term uncertainty.
- Using a local-presence ccTLD without qualifying, which can lead to suspension or deletion.
- Assuming gTLD dispute rules apply, while each ccTLD has its own procedure.
- Ignoring renewal and transfer rules, which differ from registrar to registrar for some ccTLDs.
- Expecting the same DNSSEC support everywhere; most major ccTLDs sign their zones, but registrar support for DS records varies.
Before registering, it is therefore prudent to read the registry’s eligibility and dispute policy, confirm that the chosen registrar supports the ccTLD fully, and register important brand names in both the ccTLD and a matching gTLD where budget allows.
In simple terms
A ccTLD is the country ending of a web address, such as .de for Germany or .fr for France. It tells visitors that a site is probably connected to that country.
Each country sets its own rules for who can use its ending. Some let anyone register, while others require a local address. A few endings, like .tv or .io, became popular worldwide simply because the letters look like words.
A practical example
A family-owned furniture maker in Slovakia sells mainly to domestic customers and plans a later expansion to Austria. It registers its brand under .sk as the main website, because local customers trust a national ending and search results in Slovakia favor it.
For the Austrian launch, the company also registers the same name under .at, after confirming that the Austrian registry allows registrants from other countries. It sets up a German-language site there and keeps both domains with the same registrar to simplify renewals and DNSSEC management.
Within the first season, Austrian visitors arrive mainly through the .at domain, while the .sk site keeps its domestic audience. The company gains a local presence in both markets without confusing customers.