Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
The .eu top-level domain, TLD, is run within an EU framework and the right to register and own a .eu domain name is subject to eligibility criteria – in short, being an EU citizen, or being a company established in the EU. For British citizens and companies in post-Brexit, they’ll no longer meet the criteria to register, or indeed continue to own their .eu domains.
What does this mean for British .eu domain name owners?
The domain registry in charge of all .eu domains, EURid, is working on the basis that Britain will leave the EU without a deal on 31st October 2019. Just a week or so before the date on which the UK would fall out of the EU (assuming no deal is in place, or an extension sought and granted) EURid will be sending out emails to all owners of .eu domains who are based in Britain or Gibraltar. Domain name owners will then have until the 1st January 2020 to try and meet the eligibility criteria. After this date, any domain not meeting the criteria will be withdrawn, on a practical level meaning that any website or email service attached to that domain will no longer work. Then on 1st November 2020, those domains which have been withdrawn will be fully revoked and any third party (based in the EU) will be able to register them.
Next Steps for .EU Domain Name Owners
If you or your business owns a .EU domain there are a few things you should be thinking about.
Firstly check whether your .eu domains were registered with a GB or GI (Gibraltar) country code.
For British companies with a subsidiary in the EU it would be sensible for them to transfer any .eu domains into the European subsidiary before 1st January 2020.
For UK citizens who are living in the EU, or EU citizens living in the UK they’ll still be entitled to own their domains, but should ensure that all details are updated to avoid losing the domain.
For anyone unable to fall into either of the above camps they need to start planning for losing their .eu domain from 1st January next year. If you have a business that relies on a .eu domain now is the time to start planning and think about setting up a new domain and redirecting the .eu domain as soon as possible.
It is also worth checking when your .eu domain is due to expire. If the domain expires between 1st November 2019 and 1st January 2020 it will no longer automatically renew so if you need to renew it for a couple of months to buy your business more time to prepare you’ll need to manually renew it.
StatusCake Team
Share this
More from StatusCake
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026
Make Your Engineering Processes Resilient. Not Your Opinions About AI
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
James Barnes
January 8, 2026