At 07:00 on November 8, 2005, a small technology race began in Spain. The liberalization of the .es domain made it possible to freely register thousands of names that had until then been subject to much tighter restrictions. Internet professionals stayed up to grab generic words and short domains before anyone else could. Twenty-one years later, .es is a well-established part of Spain’s digital identity, although some veteran users believe its administrative management still needs a deep modernization.
The .es liberalization at 21: the key facts in 20 seconds
- Open registration began on November 8, 2005, following Spain’s new National Domain Plan.
- That morning saw a rush of applications for generic names.
- David Carrero, co-founder of Stackscale, still holds domains from that era, including meteo.es, navidad.es, messenger.es, and root.es.
- Two decades on, criticism centers on the administrative experience, particularly around certain ownership and contact changes.
The 2005 change was far more significant than it might seem from today’s perspective. Registering a domain has become a routine operation: you search for a name, check its availability, pay, and in many cases it’s ready to configure minutes later.
.es didn’t always work that way.
During its early years it was subject to rules far more restrictive than those of international extensions like .com. The National Plan approved in 2005 changed that philosophy and sought to ease access to Spain’s country-code domain.
The liberalization culminated on that November 8 and triggered something close to a landrush: a race to register names that had been locked away for years under the previous rules.
A night at the computer, waiting for 07:00
For a generation of Spanish internet entrepreneurs and professionals, that morning remains tied to the early days of the domain business.
One of them was David Carrero Fernández-Baillo, co-founder of Stackscale (Aire Group), who recalls staying up to catch the start of the liberalization and try to register various names.
Carrero built up a collection of .es domains that morning. Some were later sold, while others remain in his portfolio more than twenty years on.
Among those he still holds are meteo.es, navidad.es, programacion.es, messenger.es, and root.es.
Those four help explain what that opening actually meant.
They’re short, generic words, or ones closely tied to recognizable internet concepts. Finding names like these available today under an established extension is extremely difficult.
In 2005, that was still possible.
Demand was so high that the infrastructure had to handle hundreds of thousands of applications. The episode exposed something the industry had been pointing out for a while: there was real interest in using .es, but the previous rules had held back part of that growth.
The liberalization fixed much of that problem.
Since then, Spain’s country-code domain has become standard for businesses, individuals, government bodies, media outlets, and digital projects. .es stopped being an extension held back by especially rigid rules and began competing much more directly with .com, .net, and other alternatives.
The problem isn’t registering a .es anymore
Two decades later, the technical conversation has shifted considerably.
Registering a .es through a registrar is a simple operation. What some professionals question is certain subsequent domain administration procedures.
Carrero points to changes related to ownership and contacts as an example.
In his experience, some of these operations can trigger multiple rounds of communication, verification, and waiting time that contrast with the administration experience offered by other extensions.
The comparison with .com is unavoidable for any professional managing domains across different TLDs (Top-Level Domains).
Changing certain data on a generic domain can typically be done from the registrar’s own panel, applying the corresponding authentication, authorization, and security mechanisms.
Under .es, some operations still depend on registry-specific procedures that can make the experience feel less immediate.
That doesn’t mean the verifications should disappear.
A change of ownership is a sensitive operation. A domain can control a website, email, corporate services, and even account recovery processes. Protecting these changes against hijacking or fraudulent modifications is necessary.
Security around .es isn’t purely a matter of internal registry procedures, either: the domain has also drawn scrutiny in recent years for a sharp rise in its use by cybercriminals running phishing campaigns, a reminder that administrative safeguards and end-user trust are closely linked.
The technical question is different: how much process is actually needed to achieve that security.
Multi-factor authentication, electronic signatures, authorization codes, audit logs, and cryptographically verifiable confirmations currently make it possible to protect critical operations without necessarily turning every change into a drawn-out process.
That’s where infrastructure designed decades ago can start to show its age.
Domain registries need a good user experience too
Managing a country-code domain has a particular quirk: it blends internet infrastructure, regulation, and administration.
But users don’t usually think in those layers.
They expect a panel that works.
From that standpoint, a registry’s user experience can matter as much as its DNS servers or the mechanisms used to protect its database.
Carrero also brings up the performance of the Dominios.es portal, saying he has experienced waits of more than 30 seconds on certain operations carried out through its request tool.
It’s an individual experience, not an independent measurement of the service’s overall performance, but it points to a question that matters a great deal in 2026.
Digital services are no longer compared only against other public administrations.
They’re compared against any internet service.
A professional used to managing cloud infrastructure, domains, certificates, servers, or networks through panels and APIs expects similar behavior from a public platform.
The technical bar has risen enormously since 2005.
Automation and APIs: the natural evolution of a modern registry
There’s another major shift since that liberalization: internet administration has become automated.
Twenty years ago, many domain-related operations commonly required manual intervention.
Today, a provider can manage tens or hundreds of thousands of domains through automated systems.
Registrars need to integrate registrations, renewals, modifications, DNS, contacts, and transfers directly into their own platforms.
That makes application programming interfaces (APIs) and automated protocols a key part of how any modern registry operates.
The EPP (Extensible Provisioning Protocol), for example, is widely used across the industry to let registries and registrars communicate and manage objects like domains and contacts through standardized operations.
Automation doesn’t remove security controls. It simply turns administrative procedures into processes that software can verify.
That difference matters as volume grows.
Someone managing two domains can tolerate a few extra steps. A company managing hundreds or thousands needs operations that are predictable, fast, and automatable.
.es also competes with hundreds of other extensions
Modernization isn’t just a matter of convenience, either.
Domains compete with each other.
In 2005, the typical choice for a Spanish project came down mainly to .com, .net, .org, and .es.
Today’s market is much larger. ICANN has added hundreds of new generic domains over the past several years, and any company can choose among numerous extensions depending on its business.
.es keeps an advantage none of them can copy: its immediate association with Spain.
For a company operating mainly in the Spanish market, a government body, a local shop, or a media outlet, that identification still carries value.
But identity also depends on how easy it is to use.
If managing one extension is more complicated than managing another, there’s a risk that some projects end up choosing .com even when .es would have better represented their connection to Spain.
It’s hard to quantify how many registrations might be lost for this reason, but administrative experience is inevitably part of a TLD’s competitiveness.
From liberalizing registration to modernizing management
The story of .es also illustrates a pattern common to many technology projects.
Big transformations get a lot of attention. The maintenance that follows gets far less.
The 2005 liberalization was a visible reform. It changed the rules, lowered barriers, and let thousands of people register names they previously couldn’t obtain.
The next transformation would likely be far less dramatic.
Improving response times. Simplifying procedures. Automating verifications. Reviewing which steps are still actually necessary. Giving registrars and users better tools. Designing processes from the perspective of whoever manages the domain.
None of that produces a night like the one on November 8, 2005.
But it could matter more to someone who’s going to hold onto a domain for thirty years.
Carrero’s own experience proves it. The names he grabbed during that opening weren’t temporary registrations: some remain under his management 21 years later.
That timeframe changes the perspective.
A domain can be registered in seconds, but its lifecycle includes renewals, DNS changes, contact updates, transfers, corporate changes, and countless operations that can repeat over decades.
The quality of a registry shouldn’t be measured only by how easy it is to get in.
It should also be measured by how easy it is to stay.
The liberalization of .es solved one of the biggest problems facing Spain’s country-code domain back in 2005. Twenty-one years later, the next improvement may lie less in the rules for getting a name and more in modernizing the infrastructure and processes needed to manage it.
For those who were online that night, there’s also an inevitable dose of nostalgia.
The internet was much smaller. Many great names were still available. And one morning at the computer could end with someone becoming the owner of meteo.es, navidad.es, messenger.es, or root.es.
Getting those domains today would be extraordinarily difficult.
Managing them, on the other hand, should be considerably easier than it was twenty years ago.
Frequently Asked Questions
When were .es domains liberalized?
Open registration began on November 8, 2005, after Spain approved its new National Domain Plan for .es names and completed a prior opening process.
Why did the .es liberalization matter?
The change removed most of the restrictions that had limited which names individuals and companies could register. It brought the way Spain’s domain worked closer to that of other widely used extensions.
Which domains did David Carrero register during that period?
David Carrero Fernández-Baillo, co-founder of Stackscale, currently holds, among others, meteo.es, navidad.es, messenger.es, and root.es. He also registered other names during that period that were later sold.
What aspects of .es domains could be modernized?
Criticism from some veteran users centers on the administrative experience of certain changes, the time some procedures take, and the case for greater automation while keeping the controls needed to prevent fraudulent changes.
