.ES Domain: Requirements, the ID Rules, and Setting It Up

You do not need to live in Spain to register a .es domain. What you do need is a valid identification number — a Spanish NIF or NIE if you have one, or a passport number, company registration number, or foreign tax ID if you do not. That single requirement is the whole of the eligibility question, and it is what the registrar forms are asking about.

The .es rules were genuinely restrictive once, and a lot of guidance written before 2005 is still circulating. They were relaxed two decades ago. What remains is an identification requirement that looks intimidating on a registrar form because it presents a dropdown of thirty legal entity types, and a contact rule that catches people out when they try to put a company name in the wrong field.

Who can register, and what changed
The contact rule that catches people out
WHOIS privacy works differently here
Syntax rules and the prohibited terms list
Setting it up after registration
Ranking in Spain, and where the site runs
How this fits the rest of the stack
FAQ

Who can register, and what changed

The .es namespace belongs to Spain and is administered by Red.es, the public entity that runs the registry through dominios.es. Before 2005, registration required a demonstrable connection to Spain and the rules were enforced. That changed, and the extension is now effectively open.

The current position, in one sentence: anyone with a verifiable identification number can register a .es domain, resident or not. Some registrars phrase this as requiring a lasting tie with Spain, which sounds like a restriction and functions as a formality — your intention to do business with a Spanish audience satisfies it, and nobody is asked to prove it.

What is real is the identification. Every .es registration records an ID type and an ID number for the registrant, and the registry validates the format. This is stricter than most extensions, where a name and an email are enough.

The ID types accepted are, broadly: a Spanish NIF, DNI, or CIF for Spanish individuals and companies; an NIE for foreign residents in Spain; or a generic identifier for everyone else, which can be a passport number, a foreign national ID, a company registration number, a VAT number, or a driving licence number.

The contact rule that catches people out

A .es registration has four contact roles: registrant, administrative, billing, and technical. The registrant may be an individual or a legal entity — a company can hold the domain.

The other three must be natural persons. Not a company, not a role address, not a department. A named human being.

In practice this means that if you register as a company, the Organization field is filled for the registrant and left blank for the admin, billing, and technical contacts, which instead carry a person’s name and their own identification. Registrar forms enforce this unevenly and the error messages are frequently unhelpful, so a submission failing on validation is usually this.

The inverse also trips people. If you register as an individual, the Organization and Job Title fields must be blank across every contact set. Filling them in with something harmless causes a rejection that names neither field.

Where you have a choice, use real people who will still be reachable in three years, and record which identification number was supplied for each. Changing registrant details on a .es later is more paperwork than on a generic extension.

WHOIS privacy works differently here

The .es registry publishes only the registrant’s name in public WHOIS. The address, phone number, and email are concealed by the registry itself.

This is a registry policy rather than a paid privacy service, so it applies to every .es domain automatically and there is nothing to buy. It also means the third-party WHOIS privacy add-on that registrars upsell on generic extensions is largely redundant on .es.

It cuts both ways. The concealment is not configurable, so if you want your contact details publicly visible — some businesses do, for trust reasons — that is not available. And the name is always published, so a domain registered by an individual shows that individual’s name.

For a business, register in the company’s name rather than an employee’s. It keeps the public record accurate, and it avoids the awkward conversation when the person named in WHOIS leaves and the domain is technically registered to them.

Syntax rules and the prohibited terms list

A .es name may contain letters, digits, and hyphens, must not begin or end with a hyphen, and runs up to 63 characters. Spanish characters including the enye are supported through internationalised domain names, which is genuinely useful for Spanish brand names and worth registering alongside the plain-ASCII version if the name contains one.

The registry publishes a list of prohibited terms, largely covering the names of public institutions, protected designations, and a set of terms reserved for administrative use. It is rarely relevant to a commercial name, but if a registration is rejected for no apparent reason and the syntax is valid, this list is where to look.

Third-level options exist — .com.es, .nom.es, .org.es, .gob.es, and .edu.es — but they are lightly used. Spanish businesses overwhelmingly use the second-level .es, and .com.es reads as a compromise rather than a category signal. Prefer the second level; if it is unavailable, consider a different name before dropping to a third level.

Setting it up after registration

The domain is a name until you publish records under it. Point the nameservers at whoever will host your DNS, then add what the site and mail need.

A record at the root for the host’s IPv4 address, or ALIAS/ANAME if your host provides a hostname.
CNAME for www pointing at the root or the host target.
MX records for mail, plus SPF, DKIM, and DMARC as TXT records.
TXT records for any service verification you need.

Pick one canonical hostname — with or without www — and 301 the other to it. Then confirm the certificate covers both, because visitors will type both and a certificate mismatch produces a browser warning that stops people cold.

If the .es sits alongside a .com serving the same business, decide deliberately which is canonical. The common arrangement is a .com for the international site and a .es serving Spanish-language content for the Spanish market, cross-referenced with hreflang. What does not work is two domains serving identical content with no signal about which is primary, which splits your search presence across both.

Ranking in Spain, and where the site runs

A .es domain tells search engines the site targets Spain, which is a real and useful signal for a Spanish audience. It also tells them the site does not target anywhere else, which is the cost.

The rest of the localisation does more work than the extension: Spanish-language content written rather than machine-translated, prices in euros, a Spanish address and phone number, and links from Spanish sites. A ccTLD sitting on top of English content is a mismatch that search engines resolve in favour of the content.

Latency matters too, and it is the part that is a hosting decision rather than a marketing one. A Spanish visitor loading from a server on another continent pays for that distance on every request, and page speed feeds directly into how a local search result performs. Serving Europe from Europe is a small choice with a measurable effect.

How this fits the rest of the stack

The registration is a one-off with an annual fee attached; the site behind it is the recurring decision. What matters after checkout is where it runs, whether the certificate covers both the root and the www form, and whether a Spanish visitor gets bytes back quickly. Custom domains and certificates on RunxBuild are set per project, so pointing a new ccTLD at an existing service is a DNS change and nothing more. For the running side, the RunxBuild hosting calculator puts the service, database, and bandwidth in one view.

Useful related references:

FAQ

Do I need to live in Spain to register a .es domain?

No. The residency restrictions were dropped in 2005. What remains is an identification requirement: a Spanish NIF or NIE if you have one, or for non-residents a passport number, foreign national ID, company registration number, or VAT number. Some registrars mention a lasting tie with Spain, which is a formality rather than something you are asked to prove.

Why does my .es registration keep failing validation?

Almost always the contact fields. The registrant may be a company, but the administrative, billing, and technical contacts must each be a natural person with their own identification. If you registered as an individual, the Organization and Job Title fields must be blank on every contact set. Registrar error messages rarely name the offending field.

Is WHOIS privacy included with a .es domain?

Effectively, yes. The registry publishes only the registrant’s name and conceals the address, phone, and email itself. It is registry policy rather than a paid service, so there is nothing to buy and nothing to switch off. Register in a company name rather than an employee’s if you would rather not publish an individual.

Should I get .es or .com.es?

The second-level .es in almost every case. Spanish businesses use it overwhelmingly, and .com.es reads as a fallback rather than a category. If the .es you want is taken, consider a different name at the second level before dropping to a third level.

Will a .es domain help my site rank in Spain?

It is a clear geographic signal for Spain, and equally a signal that you are not targeting elsewhere. Spanish-language content, local pricing and contact details, Spanish backlinks, and fast load times for visitors in Spain all carry more weight than the extension by itself.