What Happens When a Registrar Shuts Down (Google Domains Lessons)

You open your browser one morning and try to log into your registrar. The page doesn't load. Not a slow load. Not a 503 error. Just nothing. You refresh. Still nothing. You check your email for a maintenance notice. There isn't one.

Your domain still resolves. Your site is still up. But the company that holds the registration record for your domain, the company you've been paying every year, is unreachable.

Here's the question nobody thinks about until that moment: what actually happens to your domain now?

The Google Domains Story Is a Warning, Not a One-Off

In June 2023, Google announced it was selling Google Domains to Squarespace. The transition completed by the end of 2023. More than 10 million domains were moved to a new registrar without the registrants choosing to move them.

Most people who got that email were confused. Some were frustrated. A few panicked, not because anything broke immediately, but because they realized they had never thought about what their registrar relationship actually meant. They'd registered with Google because it felt safe. Google was permanent. Google was everywhere. And then one day, it wasn't their registrar anymore.

Google Domains didn't fail. It was a planned, orderly acquisition. Squarespace gave plenty of notice, the DNS records transferred cleanly for most customers, and the domains kept resolving throughout. If this had to happen, it happened about as well as it could.

But what if it hadn't been orderly?

What ICANN Actually Requires When a Registrar Fails

ICANN, the organization that oversees domain registration globally, has rules for registrar failure. Most domain owners have never read them.

Here's what the ICANN Registrar Accreditation Agreement requires:

Every accredited registrar must maintain an escrow deposit of registrant data. This means that even if the registrar goes bankrupt or shuts down overnight, the registration records, including your name, contact information, and domain details, exist in a third-party escrow account maintained by an ICANN-approved data escrow provider.

If a registrar fails, ICANN coordinates with registries (the organizations that run .com, .net, .org, and so on) to ensure domain continuity. Registrants are supposed to receive notice and have a window to transfer their domains to a registrar of their choice.

That's the rule. Now here's the reality: the transition window can be weeks. During that window, you may not have access to your registrar control panel. You may not be able to change DNS records, update nameservers, add new domains, or renew domains coming up for expiration. The domain keeps resolving on its existing configuration, but you're locked out of managing it.

For most personal sites, that's an inconvenience. For a business running on that domain, it can be a crisis.

The RegisterFly Collapse: What Unmanaged Failure Looks Like

Google Domains is not the right cautionary tale. It was too clean.

In 2007, a registrar called RegisterFly collapsed and it was messy in a way that the Google Domains story wasn't. The company had tens of thousands of customers and an ICANN accreditation. When it started failing, customers found their domains locked, support requests unanswered, and the control panel broken. Some domains expired during the chaos because owners couldn't access renewal controls.

Honestly, the thing that sticks with me about this story is how preventable it was for most of those customers. Not the registrar failure — that's outside your control. But the part where they lost access because they hadn't documented their DNS records or secured their auth codes. That part was preventable.

ICANN eventually revoked RegisterFly's accreditation and worked to transition domains to other registrars. GoDaddy handled a significant portion of the migration. But not before real damage was done. Domains lapsed. Sites went down. Businesses lost email access tied to domains they couldn't manage.

This was almost 20 years ago, and the ICANN systems have improved since. But the structural vulnerability hasn't changed: if your registrar goes dark, you are dependent on ICANN and the registries to manage the transition on your behalf, on their timeline, not yours.

The .ly Libya Case: When the Registry Itself Is the Risk

Registrar failure is one type of problem. Country-code domain risk is another.

Libya's .ly domain extension became popular with URL shorteners and tech companies (bit.ly, ow.ly, and others) because of its short, memorable pattern. Libya's government administers the .ly registry. In 2010, Libya shut down vb.ly, a domain owned by a US company, on the grounds that it violated Libyan content laws.

The domain was just gone. Not transferred to another registrar. Not placed in an escrow window. Shut down.

No ICANN escrow policy protects against this. ICANN governs generic top-level domains like .com and .org. Country-code domains (.ly, .io, .ai) are governed by the countries that own them. If the British Indian Ocean Territory government decided tomorrow to pull all .io domains, there would be no ICANN transfer window. The domains would simply stop resolving.

This isn't a theoretical risk. It's happened. The question is whether the domains you own are exposed to it.

No-Warning Suspension: The Quiet Version of This Problem

Registrar shutdown is dramatic. But there's a quieter version that happens more often.

Porkbun, a well-regarded registrar with a generally positive reputation, has a documented history of silently suspending domains without prior notice, including for terms-of-service violations that were not communicated to the registrant. The query cluster around "Porkbun silently suspended my domain" has 74,000 monthly searches. That's not a niche problem.

When a registrar suspends a domain without warning, the domain stops resolving. Not because it expired. Not because there's a DNS issue. Because the registrar unilaterally took it offline. From the outside, the site looks down. From the inside, the domain owner gets a terse email explaining that the domain has been flagged, often with no clear recourse path and no stated timeline for resolution.

This is not unique to Porkbun. Any registrar can do this. ICANN allows registrars to suspend domains for acceptable use violations, and the process for disputing a suspension is slow.

The practical implication: your domain's uptime is partially in the hands of a company whose internal compliance team you've never met.

What to Do Before This Happens to You

There are concrete steps that make registrar disruption survivable.

Document your DNS records now. Log into your registrar control panel and export or manually record every DNS record for every domain you care about. A-, AAAA-, MX-, CNAME-, TXT-records, all of it. If your registrar goes dark tonight and you have to rebuild DNS at a new registrar tomorrow, you need this information. Most people don't have it.

Use a registrar that separates registration from hosting. If you registered your domain at the same company that hosts your site, a registrar disruption can take both offline simultaneously. Separate the two. Your domain registration and your hosting should be at different companies.

Know your auth code (EPP code) before you need it. Every domain has a transfer authorization code. Registrars are required to provide it on request. Get it now, store it somewhere secure. If your registrar control panel becomes inaccessible, you'll need this code to initiate a transfer at a new registrar. Without it, you're waiting on ICANN to sort things out. See the full step-by-step on how to transfer a domain.

Read your registrar's terms of service, specifically the acceptable use and suspension clauses. You don't need to memorize it. You need to know: what can get your domain suspended, what the notice period is, and what the dispute process looks like. If that information isn't clearly stated, that's a signal about the registrar.

Enable auto-renew and keep payment information current. If your domain expires during a registrar transition, recovery is harder. Auto-renew doesn't cost you anything and removes one failure mode. For more on why renewal economics matter, see why renewals cost more.

Choose a registrar that supports DNSSEC and has a real support path. DNSSEC won't prevent a registrar shutdown, but it signals that the registrar takes infrastructure seriously. More importantly, you want a registrar with a support structure that can respond to urgent problems, not just a ticket queue with three-day response times.

For a full comparison of registrars that actually perform well over time, see best domain registrars for long-term ownership.

What to Do If It's Already Happening

If your registrar is unreachable right now:

Check if the domain still resolves. Go to a DNS lookup tool and see if your domain returns the right records. If it does, your site is still up even if your control panel is dark. This buys time.

Check ICANN's registrar status list. ICANN maintains a public list of accredited registrars and their status. If your registrar has been suspended or terminated, ICANN will have a notice there with guidance on how to proceed.

Contact the registry directly if needed. For .com and .net domains, that's Verisign. For .org, it's the Public Interest Registry. Registries can sometimes assist with emergency unlocking when a registrar has failed.

Initiate the ICANN RAA transfer process. If your registrar is unresponsive and you can't get your auth code, ICANN's Registrar Transfer Dispute Resolution Policy has a process for this. It takes time. The sooner you start, the better.

Don't wait for the domain to expire. An expired domain is significantly harder to recover than an active domain. If your domain is approaching expiration during a registrar disruption, flag this to ICANN immediately.

This article is part of the Sprint 2 Registrar Reality cluster. If you're also wondering whether your registrar can actively block you from moving your domain, read can your registrar hold your domain hostage.