If your web host shut down and your site is gone, the files are almost never recoverable from the host itself. What you can still get back is your domain, archived page snapshots, and any email that lived somewhere else. Everything else depends on whether you kept an off-site backup you control.
A biopharma with 740 websites and 11 different hosts
Meridian Therapeutics did not call us about a shutdown. They called us because nobody could answer a simple question: which vendor is site number 412 on?
Over years of product launches, regional campaigns, and acquisitions, the company ended up with more than 740 websites spread across 11 hosting vendors. Each one had its own login, its own billing contact, and its own idea of what a backup was. Some sites were built by agencies that no longer existed. A few were paid for on a credit card that belonged to someone who had left the company.
The failure mode was not dramatic. A site would break, or get hacked, and it would sit there. Problems went unnoticed for over a week. A marketing manager in another country would eventually notice a broken product page and file a ticket, and by then nobody could say when it broke or who was supposed to fix it.
That is exactly the shape of a company that loses sites when a vendor folds. If you do not know a site exists, you will not notice the shutdown notice. If you do not know where the backup is, you have no backup.
The work was boring and it mattered. We built the inventory first: every domain, every DNS record, every host, every WordPress version, every backup location. Then we pulled the sites onto one stack with daily off-site backups and put all 740+ under monitoring that runs around the clock. Issues now surface within hours instead of a week later, and the cost of running the fleet dropped by half. The full story is in the Meridian Therapeutics case study.
The lesson generalizes to a single site just as well as to 740. A host shutdown only destroys your business if the host is the only place your business exists.
What happened when Tripod and Lycos shut down
Tripod started in 1994 and became one of the first places ordinary people could publish a page without knowing a server from a sandwich. Lycos bought it in 1998. For close to thirty years it kept running, mostly quietly, mostly forgotten by everyone except the people whose pages were still there.
In April 2026 it went dark. Customers got notice, technically, in the way these things always happen: an email to an address some people had not used since 2007, a banner on a dashboard nobody logged into. There was no useful export tool. When the servers stopped answering, family memorials, band pages, small business brochure sites, and a fair amount of internet history stopped answering with them.
Nobody in that group did anything wrong. They trusted a company to keep a promise the company never actually made. Free and cheap hosting plans almost never carry a data return guarantee. When the servers go, so does the data.
This is not rare. Hosts shut down, get acquired and gutted, or suspend accounts with little warning. We have written about a multi-day outage that left customers with no answers at UltaHost and about a host that suspended an account before the invoice was even due. Different companies, same exposure.
How to tell if your web host is dying
A host rarely announces the end. It leaks signals for months first. Watch for these:
- Support gets slower every month. Tickets that used to close in a day now take four, and answers start sounding copy-pasted. Staff reductions show up in response times before they show up in press releases.
- The control panel stops changing. No new PHP versions, no new features, no security notices. Nobody is being paid to maintain it.
- An acquisition is announced and the brand goes quiet. Acquired hosts often get migrated, repriced, or wound down within 18 months.
- Billing behavior turns aggressive. Surprise renewals, new mandatory add-ons, or accounts pushed to collections fast are signs of a company squeezing cash.
- The status page stops matching reality. Your site is down, the status page says all systems operational, and nobody updates it for hours.
One of these is noise. Three of these at once is a countdown. We covered the full pattern in nine signs it's time to switch WordPress hosts, and the same triage order applies when you cannot tell whether you are looking at a dead host or something simpler. Before you panic, check DNS first, because a lapsed record looks exactly like a hack or a shutdown.
How to recover a website after your host shuts down
Start with what still exists outside the host. Work in this order: domain, archives, email, then rebuild. Here is what each asset realistically gives you back.
| What you lost | Where a copy might exist | What you actually get back |
|---|---|---|
| Page text and layout | Wayback Machine, search engine snippets, old proposals or PDFs | Readable content, page by page, often missing recent updates |
| Images and PDFs | Wayback Machine, your designer's files, email attachments | Some originals, many at thumbnail size or missing |
| Database (posts, users, orders) | Only your own export or off-site backup | Nothing, if you never took one |
| Domain name | Your registrar, if it is separate from the host | Full control, as long as renewal is current |
| Email and mailboxes | Google Workspace, Zoho, or your desktop mail client's local cache | Everything, if mail did not live on the host |
| Form submissions and leads | Your CRM, notification emails in your inbox | Whatever was forwarded at the time |
According to the Internet Archive, the Wayback Machine holds more than 900 billion archived web pages (2025), so odds are decent that your home page and main service pages were crawled at some point. Use the calendar view, pick a date before the host went dark, and save each page as HTML. Right-click and save images individually. It is slow, manual work. It is also the only copy you have.
The domain is the piece most people get wrong. If you registered your domain through the same company that hosted your site, the registrar side may still be operating even after the hosting side stops. Log in, confirm the expiration date, and unlock the domain so you can transfer it to a registrar with no ties to the host. If the registration itself is stuck in a dead company, file a transfer dispute with the registrar of record and be patient.
Email is the other quiet casualty. If your mailboxes ran on the host's shared mail server, they are gone and so is the address that receives password reset emails for everything else. That is one of several reasons your host's free mailboxes are not a business email plan. Move mail to a provider that has nothing to do with your hosting, before you need to.
What owning your website actually means
Owning a website means four things live in places a single vendor's failure cannot touch:
- The domain, at a registrar separate from your host, with auto-renew on and contact details that reach a person.
- DNS, at a provider you control, so you can point the domain at a new server the same hour you need to.
- A current off-site backup, stored somewhere other than the server it came from, including both files and database.
- A restore you have tested, because an untested backup is a hope, not a plan.
Most people have one or two of these. Few have all four. WordPress makes the fourth one easy to skip, since the site keeps working and the backup plugin keeps saying "success" even when it is writing copies to the very disk that is about to disappear. We laid out what a real plan covers in our guide to what a WordPress backup strategy needs to include.
According to W3Techs, WordPress runs about 43% of all websites (2025), which means the single most common recovery scenario on the internet is a WordPress site, a dead server, and an owner discovering their backups were on that server.
A portability checklist you can run this week
Set aside an hour. Work through it in order.
- Open your registrar account and confirm the domain expiration date, the renewal card, and the admin email address. Write the expiration date on a calendar.
- Confirm your DNS is managed somewhere you can log into independently. Cloudflare's free tier is fine.
- Find your most recent backup. Download it to your own machine right now. If you cannot find one, that is your answer.
- Open that backup. Confirm it contains both a database file and a wp-content folder. A file that only holds themes is not a backup.
- Restore it somewhere: a staging site, a local install, anywhere. Confirm the home page loads and the posts are there.
- Check where your email lives. If the MX record points at your host, plan the move.
- Write down, in one document, every vendor that touches the site: registrar, DNS, host, mail, CDN, payment gateway. Store it somewhere two people can reach.
That document is the same inventory we built for Meridian, only shorter. It is also the thing that turns a host shutdown from a disaster into a Tuesday.
How TopSyde handles this
Every site we manage gets daily off-site backups stored away from the production server, plus monitoring that runs 24/7 so a broken site does not wait for a customer to report it. Migrations are portable by design. If you ever leave, you get a complete, working copy of your site and database, because a hosting relationship should be something you stay in by choice.
Plans start at $89/mo per site, and support is handled by senior developers who reply in under 2 hours during business hours. You can see exactly what is included on the spec sheet, compare it on the pricing page, or read how the model works for larger fleets on our enterprise hosting page. If you are new to the category, start with what managed WordPress hosting covers in 2026.
Frequently Asked Questions
Can I get my files back after my web host shuts down?
Usually not from the host. Once the servers are decommissioned the data is gone, and free or budget plans rarely include any data return obligation. Your recovery options are the Wayback Machine for page content, your own off-site backups, and any files your designer or agency still has.
How much of my site can the Wayback Machine actually restore?
Text, page structure, and some images, depending on how often the crawler visited. It cannot return your database, so posts that were not crawled, user accounts, WooCommerce orders, and form submissions do not come back. Treat it as a way to rebuild content, not as a restore.
What happens to my domain name if my host goes out of business?
If the domain is registered with a different company than your host, nothing happens to it. You just point DNS at a new server. If the host was also your registrar, log in immediately, unlock the domain, and transfer it out while the registrar side is still operating.
How often should I take an off-site backup?
Daily for any site that changes, and immediately before updates or migrations. The key word is off-site: the copy has to live somewhere other than the server it came from, because a server failure or account termination takes local backups with it.
Is a backup plugin enough on its own?
Only if it writes to remote storage you control and you have tested a restore from it. Plenty of plugins default to saving backups inside wp-content on the same server, which protects you from a bad plugin update and from nothing else.
DevOps & Security Lead
12+ years DevOps, Linux & cloud infrastructure certified
Marcus leads infrastructure and security at TopSyde, managing the server fleet and AI monitoring systems that keep client sites fast and protected. Former sysadmin turned WordPress hosting specialist.
