European country-code domains for founders: .de, .fr, .nl, and EU domain hacks

If you are building for one European market, a country-code domain is usually a good idea — and often the strongest trust signal you can put in an address bar. Europeans use these extensions at serious scale: Germany’s .de, run by DENIC, a Frankfurt-based member-owned cooperative founded in 1996, has more than 18 million active registrations, making it the largest ccTLD in Europe and second only to China’s .cn worldwide. The catch: every ccTLD is run by its own national registry, and the folklore about the rules is often years out of date. Some of the big European extensions are open to anyone on the planet; others genuinely do require residency — just not always the ones you would guess.

When does a local ccTLD build trust — and when does it hold you back?

A national extension tells visitors three things before they read a word of your site: you operate in their market, you probably speak their language, and you are committed enough to register locally. For a founder selling into Germany, a .de domain does that work on sight in a way no generic extension can. The same goes for .fr in France or .nl in the Netherlands — the extension is a flag, and flags are read instantly.

The trade-off is that the flag is stitched into your brand. A ccTLD works beautifully while your market and your extension match, and starts working against you the moment they don’t. Expand from Germany into France and you face a choice: run a parallel .fr site, migrate the whole brand to a neutral extension, or keep asking French customers to trust a German address. None of those options is free.

The usual advice, for what it’s worth, splits on ambition. One-market businesses take the local ccTLD. Pan-European businesses look at .eu — its eligibility rules mean an .eu registrant is verifiably based in the EU/EEA, which functions as a light credibility signal of its own; we weigh that option properly in is a .eu domain worth it?. And globally ambitious businesses still tend to treat .com as the default, with many EU companies registering both and redirecting. Treat that as framing rather than law — but decide which of the three you are before you register anything.

What are the actual rules for .de, .fr, .nl, .es, and .it?

Here is where the folklore needs correcting. A claim still circulating on domain blogs is that “.de and .fr require a registered local business.” That is outdated for .de and imprecise for .fr. The current picture, registry by registry:

• .de (Germany, DENIC). Open worldwide — the local-presence requirement was dropped in May 2018, and no German business is needed. The one administrative wrinkle: if you are outside Germany, you must name an authorized recipient (Zustellungsbevollmächtigter) with a German address who can receive legal and court documents. One thing changed recently: under Germany’s NIS-2 implementation, which took effect on 6 December 2025, DENIC has published public WHOIS data for legal-entity registrants — register as a company and your business name, address, email, and phone number are now visible in WHOIS, where they were largely redacted before. Individual registrants’ personal data stays redacted. A second phase, adding automated risk assessment of registration data, followed in April 2026 — so keep your holder details accurate or you risk a verification request.
• .fr (France, AFNIC). This one really is restricted, but by residence, not nationality and not a French company. Individuals must reside in the EU, Switzerland, Norway, Iceland, or Liechtenstein; organisations must be established there. A founder living anywhere in the EU qualifies — you do not need any connection to France specifically. AFNIC runs eligibility checks and verifies registrant data accuracy and reachability. Worth being precise about why, since it’s easy to assume: France had not yet transposed the EU’s NIS2 Directive at the time of writing, and AFNIC’s publication of organisation data long predates it under French domestic law. The practice is French, not NIS2-driven.
• .nl (Netherlands, SIDN). Open, with no residency requirement in practice. The registration technically requires a Netherlands address, but SIDN resolves that itself by auto-assigning a “domicile address” to registrants who don’t have one — so foreign founders can register without friction.
• .es (Spain, Red.es). Open worldwide with no residency or local-presence requirement. You do have to supply valid identification — a passport, national ID, or tax/VAT number — so registration is not anonymous, but it is not geographically gated.
• .it (Italy, Registro.it). Restricted: you need citizenship, residence, or a registered office in the EEA, Vatican City, San Marino, Switzerland, or — notably — the United Kingdom, which kept its .it eligibility after Brexit even as it lost .eu. One honesty note: the registry’s own policy pages could not be verified directly at the time of writing, and this list comes from multiple agreeing secondary sources — so confirm eligibility with your registrar before building a brand on it.

The pattern worth internalizing: “European ccTLD” tells you nothing about eligibility on its own. Two of the five biggest are fully open, one is open with an administrative formality, and two are genuinely restricted — but both restrictions are satisfied by ordinary EU residence, not by incorporating locally.

Which domain hacks are actually European?

Country-code extensions double as raw material for domain hacks — names built across the dot, like youtu.be — and if part of your pitch is being an EU company, it pays to know which “European-sounding” extensions are actually European. The technique itself is covered in domain hacks explained; here is the geography.

Genuinely EU: .it is Italy, an EU member, and reads as the English word “it” — a gift for any brand ending in -it. .at is Austria, also an EU member, and reads as “at.” A hack on either keeps your address inside the Union, with the eligibility caveats above (.at aside, remember .it’s restricted list).

In the neighbourhood but not in the club: .me is Montenegro — an EU candidate country, not a member — and its popularity for personal branding doesn’t change that. .is is Iceland, which is in the EEA and EFTA but not the EU.

Not European at all, despite the vibes: .sh is Saint Helena, a British Overseas Territory in the South Atlantic. .io is the British Indian Ocean Territory. .ly is Libya. All three power famous hacks, and none of them puts your domain under an EU registry.

Does this matter? Only if you make it matter. If your positioning leans on being EU-based — and for many buyers that is exactly the appeal — an .io or .sh address quietly contradicts the story your marketing tells. If the hack is just wordplay, register whatever reads best.

How do you choose one?

Start from your market, not the extension. One country: take its ccTLD, checking the eligibility notes above. Pan-European: weigh .eu against a neutral generic. Global: default to .com or a strong generic, and consider defensive ccTLD registrations in core markets later. The hard part is finding a name that is available under whichever rules apply — which is what the domain.yoga generator is for: describe what you’re building, and it proposes names with live availability across extensions, so your shortlist only contains domains you can register today.