The failure everybody actually has
One company holds the domain, the DNS, the server and the backups, and the account is in a name that can be looked up. Every one of those is a switch, and they are all wired to the same person’s decision. That is not an infrastructure, it is a single point of failure with four labels on it.
Resilience here does not mean uptime. It means that no single decision by a single party ends the project.
Separation one: registrar away from host
The highest-value change and the cheapest. If the company that suspends your server is also the company holding your domain, you lose the address as well as the building, and the address is the part your audience knows.
Put the registration somewhere that does no hosting, lock the domain, and keep the registrar account on an email address that is not hosted on the server you are protecting. That last clause is the one people miss, and it is how a recoverable situation becomes a circular one.
Separation two: DNS away from both
DNS is the steering wheel. If you control it, moving hosts is a record change and a short TTL. If your host controls it, moving is a negotiation with the party you are trying to leave.
Keep TTLs low as a standing posture — three hundred seconds costs nothing measurable and turns a two-day cutover into a five-minute one on the day you cannot afford two days.
Separation three: backups out of reach
A backup inside the account being suspended is not a backup. It needs to be a different provider, ideally a different country, and it needs pull-based credentials that the production server cannot use to delete history — otherwise anything that compromises the server also destroys the backups.
- Off-site, different provider, different jurisdiction where it matters.
- Append-only or versioned, so a wipe on the source is not a wipe on the copy.
- Restored once, onto a different machine, by you, before you need it.
- Encrypted, with the key held somewhere that is not the backup.
Separation four: jurisdiction
This is the one that costs money and is the reason the other three are not enough. If the company holding your disk is obliged to obey a notice, then no amount of DNS discipline helps — you will simply be moving quickly, repeatedly, forever.
What matters is not the country in the region name, it is which company is answerable and where. A US provider with a Frankfurt region is a US company answering US process about a server in Germany. That distinction is the whole subject of one of the comparisons and it is the most commonly misread thing in this market.
Separation five: identity
Everything above assumes the pressure arrives at your supplier. Sometimes it arrives at you — through a registrar record, a payment trail, or an invoice with your company name on it.
If your work needs that not to happen, the account itself has to hold nothing worth demanding. That is a product decision made before you sign up, not a setting you can change afterwards: an address and a password, settled in crypto, with the full inventory of what is held published in advance.
An afternoon’s work, in order
- Move the domain to a registrar that does no hosting. Lock it.
- Move DNS to a third party you control. Drop TTLs to 300.
- Set up an off-site, versioned, encrypted backup. Run it.
- Restore it onto a scratch machine. Actually do this one.
- Write down the recovery order and where the keys are. On paper is fine.
- Then, and only then, think about where the servers should live.
Steps one to five are free or nearly so and cover most of the damage. Step six is the one this business sells, and it is deliberately last: a host that tells you to fix your jurisdiction before you have a tested backup is selling rather than advising.
Questions people actually ask
Is this paranoid for a small site?
Steps one to five are ordinary competence and take an afternoon. Step six depends entirely on whether anybody has a reason to complain about what you publish.
Does a CDN protect me?
From traffic, yes. From a takedown, no — a CDN is one more party that can be asked to stop serving you, and they are asked often.
What about hosting it at home?
It removes the host and adds your ISP, your address and your electricity bill. That is a different threat model, and usually a worse one.
How many jurisdictions is enough?
One that is genuinely outside the complainant's reach beats five that are not. The number matters less than whether a separate company stands behind each one.
Written by the people who answer the notices, and corrected when it is wrong. Last revised 30 July 2026.
Every price on this estate is published in full, in one place. See the whole catalogue