.eu vs .com vs Country TLD: Which to Register?
By NorwegianSpark Editorial — written with AI assistance and reviewed by the NorwegianSpark SA editorial team
The question underneath the question
Nobody actually wants to know which extension is "best". What they want to know is: which one puts my business in front of the customers I am trying to reach, without creating an administrative problem I will still be paying for in five years.
That reframes it usefully. A domain extension is a claim about where you belong. A country-code extension claims one country loudly. A .com claims nowhere in particular and therefore everywhere. And .eu claims a bloc, with a membership test attached. Pick the one whose claim matches the business you actually run.
What Google does with the extension, in Google's own words
This part is not folklore, and it is worth quoting rather than paraphrasing. Google's documentation on managing multi-regional sites says of country-code top-level domains that they are "tied to a specific country (for example .de for Germany, .cn for China), and therefore provide a strong signal to both users and search engines that your site is explicitly intended for a certain country." Of the alternative it says: "Generic top-level domains (gTLDs) are domains that aren't associated with specific locations."
Checked at developers.google.com on 6 September 2026.
Read that carefully, because it cuts both ways. A ccTLD is a strong signal for one country, which also means it is a weak signal for every other one. Google's own list of drawbacks for the ccTLD approach includes that it is costly, that availability is limited, that requirements can be strict, and that it targets a single country. Those are not our objections; they are the search engine's.
The practical translation: if you sell in one country, the ccTLD is doing work for you. If you sell in six, you are either buying six domains or you are asking one ccTLD to rank outside its country, which is the one thing the signal is designed not to do.
The three options, side by side
| Local ccTLD (.de, .fr, .it, .pl…) | .eu | .com | |
|---|---|---|---|
| Geographic signal | Strong, one country | Bloc-level | None by default |
| Who may register | Set by each national registry; often restricted | Restricted, see below | Anyone |
| Best when | One country is the whole market | Several member states, one brand | Any audience outside the bloc |
| Main risk | Invisible outside its country | Eligibility must be maintained | No built-in local signal |
| Second-domain habit | Usually paired with .com | Usually paired with .com | Usually paired with a ccTLD later |
Who may actually register .eu
This one has a real, published eligibility test, and it is the single most common reason a .eu order fails. EURid, the registry, states the criteria as follows:
"You may register a .eu, .ею or .ευ domain name if you fulfill the following criteria: You represent an organisation established in one of the European Union Member States; or Iceland, Liechtenstein or Norway. You are an individual residing in one of the European Union Member States, Iceland, Liechtenstein, or Norway, or a citizen of one of the European Union Member States, Iceland, Liechtenstein, or Norway (as of 2 August 2021)."
Quoted from EURid's own help centre, checked 6 September 2026.
Three things follow from that text, and all three surprise people:
- Citizenship counts on its own. A citizen of a member state, Iceland, Liechtenstein or Norway qualifies. Where they live is a separate route to eligibility, not a second requirement stacked on top.
- Iceland, Liechtenstein and Norway are in scope even though they are not EU member states. If you assumed .eu meant "EU only", the registry disagrees with you.
- Eligibility is a standing condition, not a one-off check. It is tested at registration and it is the registry's to enforce afterwards. If the qualifying entity dissolves or the qualifying person's status changes, that is a live problem, not a historical one.
If your business does not clear that test, .eu is not a strategy question. It is simply unavailable, and the correct move is a ccTLD where you do qualify, or .com.
The rule that applies to every country extension
Each national registry writes its own rules, and they differ far more than the marketing suggests. The categories of restriction you will meet are:
- Open. Anyone, anywhere, may register. Several European ccTLDs work this way and are effectively used as generic extensions.
- Local presence required. You need an address, a company registration, or a national identifier in that country. Some registries accept a nominated local contact or a trustee service in place of your own presence.
- Documented eligibility. The registry wants evidence — a company number, a trademark, a professional registration — and will hold or cancel the name without it.
- Second-level structure. Some countries register under a second level (a commercial prefix before the country code) rather than directly under the country code, and the two are not interchangeable.
Never take the requirement from a reseller's product page. Take it from the registry that runs the extension. Resellers summarise, summaries go stale, and the party that can cancel your domain is the registry, not the shop.
Where you genuinely cannot meet a local requirement, specialist registrars exist for exactly this — see our EuroDNS review for what a ccTLD specialist actually does differently from a general registrar.
What this costs, honestly
We are not publishing a price table here, and the reason matters. Country extension pricing is set per registry, resold at different margins by every registrar, and moves. A table written today misleads a reader next quarter, and the number they will act on is the wrong one.
What is stable is the shape of the cost, and that is what to check before you buy:
- The renewal price, not the first-year price. On several European extensions these are the same figure; on others they are not close. The renewal is the number you will pay for as long as you own the name.
- Whether transfer out carries a fee, and whether the registry requires anything unusual to release the name.
- Whether privacy is available at all. Some registries publish organisation data regardless of what your registrar sells you.
- Whether restoring an expired name after the grace window costs a redemption fee, and how large it is at that specific registry.
Read all four in the registrar's own checkout, on the day you buy. Our cheapest way to register a domain walks through the method for comparing them without being caught by an introductory rate.
The dual-domain habit, and when it is a waste
The standard advice is to hold both: the ccTLD for the local market and the .com as the international face. For a company with real ambitions beyond one border, that advice is sound, and the second domain is cheap insurance against a competitor holding the obvious alternative.
The honest counter-argument is that it is oversold. Two domains means two renewals, two sets of DNS records, two certificates, and a redirect that somebody will eventually break during a migration. If you sell to one country, in one language, with no plan to change that, the second domain is a line item that buys you a defensive feeling rather than a customer. Buy it if the name is genuinely contestable. Do not buy it because a checkout upsold you six extensions at once.
And if you do hold both, pick one as canonical and redirect the other. Two live copies of the same site on two extensions is the worst configuration available: it splits every signal and doubles the maintenance.
How to decide, in order
- One country, one language, no export plan — local ccTLD, and check the registry's eligibility rules before you fall in love with the name.
- Several member states, one brand, and you clear the eligibility test — .eu, with the local ccTLDs added later only where you open a real local operation.
- Any meaningful audience outside the bloc — .com first. Add ccTLDs as you enter markets properly, not speculatively.
- You cannot meet a local requirement and .eu is out — .com, and use the site's own structure and language signals to do the geographic work instead. Google's documentation is explicit that a gTLD carries no location signal by default, so that work has to be deliberate.
Where to go next
For the general explanation of what a country extension is and how it differs from everything else, start with our ccTLD guide — that page is the broad primer and this one is the European decision. If you are still choosing between extension families rather than countries, every domain extension explained covers the wider field, and how to choose a domain name covers the name itself, which matters more than the extension does.
Last updated:
