Hosting Company Shut Down? What to Do About Your Website in the Next 24 Hours

If your hosting company shut down, your website is offline right now and you want it back today. That is usually doable. The version people describe to us on the phone is always the same: they type their own address, nothing loads, and it feels like the website disappeared from the internet overnight. Before you buy anything or cancel anything, give it fifteen minutes of checking. When an owner tells us my web hosting company went out of business, it's often something else broke and the host is still running.

We're a web studio near Seattle and we've pulled clients off hosts that had already stopped answering the phone. Here's the order we work in, because order matters more than speed. Doing step four before step one is how people lose the domain along with the site.

Is it really the hosting company that shut down?

A website can vanish for four unrelated reasons and they all look the same from your side of the screen. Match your symptom against this before you accept the worst explanation.

The last row is the one this article is written for. If the host's own homepage does not load, their billing portal is gone, and support email bounces, you are dealing with a company that has stopped operating rather than a bad afternoon. Our guide to why a website says account suspended covers the second row, and what happens if my domain name expires covers the third.

The first hour, in order

1. 1Confirm the host is really gone. Try the host's own website, their status page, and their support email. A company winding down often leaves a notice on the homepage for a while before the lights go out completely.
2. 2Try to log in to the hosting control panel anyway. Even a host that has stopped answering tickets may leave the panel running for days or weeks. This is your best window and it closes without notice.
3. 3Download everything you can, right now, in whatever mess it comes in. A messy copy of your files beats a tidy plan you execute tomorrow. Our walkthrough on how to get your website files from your hosting company has the exact clicks for cPanel, FTP, and WordPress.
4. 4Find your domain registrar. This is the single most important step, because the domain is the asset you keep and the lever you pull to get back online. It is often a different company from the host.
5. 5Check whether your email is down too. If mail ran through the host, it stopped with them, and you may be losing customer enquiries silently while you read this.
6. 6Find any backup you already have. A backup plugin's cloud folder, an old zip a developer sent, a staging copy, a file on a laptop. Check before you assume there is nothing.
7. 7Write down what you have found. Registrar, host, DNS provider, email provider, what you were able to download, what you could not. Whoever helps you next will ask for exactly this list.

Your domain is the part you almost certainly still own

Hosting and your domain name are separate purchases, usually from separate companies. That separation is what saves you. The host holds your files. The registrar holds the name. If the host is gone but the registrar is fine, then your website has not been taken from you. It has been unplugged, and you still hold the plug.

Log in to the registrar and confirm three things: that the domain is not expiring in the next few weeks, that you can edit the nameservers or DNS records, and that the contact email on file is one you can actually read. That last one catches people out constantly, because the address on the record is often a developer's or an old employee's.

Check email separately, because it fails separately

Plenty of small businesses had their mailboxes on the same hosting account as the website, which means the host taking mail down took the business's inbox with it. Others run mail through Google Workspace or Microsoft 365, in which case email keeps working perfectly while the website is a blank page. You need to know which you are, today, because customers emailing a dead mailbox get a bounce and assume you closed.

If mail was on the host, the fastest patch is to point your domain's mail records at a mailbox provider you can sign up for in twenty minutes, then forward or recreate the addresses people actually write to. Old messages sitting on the dead server are a separate and harder problem. If the mailboxes were set up with IMAP on someone's phone or laptop, that device may still hold a full local copy, so stop that device from syncing before anything overwrites it.

Day one: put something back in front of customers

You do not have to have the real website ready to stop losing business. A single page with your name, your phone number, your hours and a line saying you're online again shortly will hold the fort. Set that up first and the rest of the work stops feeling like an emergency. The steps below involve DNS settings, which is genuinely fiddly if you've never touched them. Most new hosts will do this part for you for free if you ask, and it's also a five-minute job for any developer or for us, so don't feel you have to be the one clicking the buttons.

1. 1Buy hosting somewhere reputable. Any mainstream host will do for a temporary page. You are not making a ten-year decision today.
2. 2Lower your domain's DNS TTL if you can. TTL is how long other computers are told to remember your old settings. Dropping it to five minutes before you change anything means the switch takes minutes rather than most of a day.
3. 3Point the domain at the new server. At the registrar, either change the nameservers to the new host's, or edit the A record to the new server's IP address. If your email lives elsewhere, copy the MX records across before you touch nameservers, or you will knock mail out while fixing the website.
4. 4Upload a holding page. Name, phone, email, address, hours, one sentence of explanation. Plain HTML is fine, and most new hosts have a simple built-in page builder if you'd rather not touch code.
5. 5Tell people. A post on your Google Business Profile and your social accounts costs nothing and stops the rumour that you've gone under.

The next day: restore or rebuild

Now that customers can reach you, work out which of these you're in.

• You got a full backup off the old host. This is the good outcome. Upload the files, import the database, update the site's saved address if it changed, and reissue the SSL certificate on the new server. A WordPress site typically comes back the same day.
• You have a partial copy. Maybe the files but not the database, or an export of your posts but not your images. It's a patch job, but it's much faster than starting over, and it means the words and pictures you paid for aren't lost.
• You have nothing. Do not assume the site is gone. Old copies of your pages often survive in public archives, and a developer, a designer, or a former staff member may still have a folder. Our guide on how to recover a deleted website covers the order to try things in and when starting fresh is honestly the cheaper answer.

Whichever bucket you're in, resist the urge to make it better while you rebuild. Get the old site back exactly as it was, live, indexed, and working. Improvements are a project. This is a recovery.

How to make sure this never happens again

Almost every part of this crisis comes from the same root cause: everything lived in one account at one company, and nobody at your business held a copy of anything. Fixing that takes an afternoon.

1. 1Register your domain somewhere separate from your hosting. Different company, account in the business's name, billing on a card that won't expire quietly.
2. 2Put an off-site backup on a schedule. Files and database, copied somewhere that is not your host, running automatically, at least weekly. A backup stored only on the server it is backing up is not a backup.
3. 3Test a restore once. An untested backup is a hope. Restoring one to a staging site once a year is how you find out the database was never being included.
4. 4Keep contact details on the accounts current. Renewal and shutdown notices go to whatever address is on file. If that's an old developer's inbox, you will not see the warning.
5. 5Write down what you own. A one-page document with your registrar, host, DNS provider, email provider, and the login email for each. Keep it somewhere that isn't the website.

If you'd rather hand this to someone

Everything above is genuinely DIY if you have a spare day and a reasonable tolerance for control panels. Plenty of owners do it themselves and are fine. If you'd rather not, managed hosting is included in our care plans from $99 a month, which means we hold the hosting account, run daily off-site backups, and move your site over from whatever host it's on now. The maintenance plan side of it is the part that matters here: someone whose job it is to notice, and a backup that already exists on the morning you need one.

If you want the fuller picture of how these shutdowns unfold, read what happens if your web host goes out of business. And if the host is still standing but has gone strangely quiet, the warning signs are worth knowing before the servers go dark.