Moving a site after your host suspends it

A suspension email usually gives you a deadline that has already partly elapsed, and access that is already partly gone. Panic wastes the window. Work in this order.

First: get the data out

Before anything else, before you write a single reply, pull everything off the machine. Many providers suspend network access but leave a rescue console or a snapshot export available; some leave the machine running and only null-route the public address. Whatever is still reachable, use it now. Databases first, then user uploads, then configuration. Application code is usually reproducible; a database is not.

If the panel offers a snapshot or image export, take it even if you never intend to use that format. A blob you can mount later beats a perfect backup you did not have time to make.

Second: shorten your DNS TTL

Drop the TTL on the affected records to sixty seconds immediately. This is a thirty-second change that determines whether the cutover later takes two minutes or six hours, and it costs nothing to do before you know where you are moving to.

Third: pick a destination that does not repeat the problem

1. 01Check the jurisdiction, not the marketingA provider registered in a permissive-sounding country but renting racks in Virginia inherits Virginia. Ask where the metal physically is.
2. 02Ask who is upstreamA reseller can be pressured by whoever it rents from. Hosts that own their hardware have one fewer party able to unplug you.
3. 03Read the acceptable use policy properlyA policy that lists real categories is a policy someone thought about. A policy that just says "no illegal content" tells you nothing about what happens on Monday morning.
4. 04Pay in a way that cannot be reversed against youA card gives a processor the power to freeze the account under pressure. A prepaid crypto balance does not have that failure mode.

Fourth: rebuild deliberately

The temptation is to restore the exact same stack in an hour and go back to sleep. Resist it slightly. Put the origin somewhere quiet and keep the public face on a proxy, so the next complaint reaches a layer you can replace in minutes rather than the machine holding your database. Take a backup that leaves the provider entirely — an encrypted vault somewhere unrelated is worth its trivial monthly cost the first time you need it.

Then keep the old provider paid up for a fortnight if you can. Occasionally something you forgot resurfaces, and access is easier to retain than to recover.

Published by NoDMCAVPS, an offshore host that files automated DMCA notices instead of forwarding them. What we still remove is listed in the acceptable use policy.