ENHEIT

payless.host

A backup plan that survives your host failing

Updated Nov 22, 2026

Keep a local copy that updates automatically

Download your entire site to your own machine on a schedule. Most control panels offer automated backups you can pull via SFTP or a plugin, but those live on the same server you are trying to protect against. A script that runs weekly and pulls files to a machine you control means you have something to restore from the moment the host becomes unreachable. Losing a week of posts is recoverable; losing everything because the only backup was on the same disk is not.

Store database exports somewhere other than the host

Your database is not your files. A WordPress site can be rebuilt from themes and plugins, but the posts, users, and settings live in MySQL. Export it weekly and send the SQL file to cloud storage—Dropbox, Google Drive, an S3 bucket—anywhere that is not the server it came from. A file backup without a database backup is half a backup.

Use DNS that lives outside your hosting account

If your domain's nameservers point to your host's infrastructure and that infrastructure goes offline, you cannot redirect traffic until the host comes back. Moving DNS to Cloudflare, Route 53, or another dedicated service means you can point your domain at a new server the moment you need to, without waiting for a control panel that may not load. The cost is usually zero; the time saved when a host is offline is measured in hours.

Test a restore at least once

A backup you have never restored is a backup you do not know works. Spin up a local environment or a cheap VPS once a quarter and restore your files and database to it. If the site does not load, you learn that now rather than during an outage. The fifteen minutes this takes will feel like time well spent the first time a host disappears without warning.

Document what the site needs to run

A list of PHP version, required extensions, cron jobs, .htaccess rules, and any server-level config is the difference between restoring a site in an hour and spending a day guessing why it will not start. Keep this in a text file outside the server—on your machine, in a private repo, anywhere you can reach it when the host cannot be. If you have ever moved a site and discovered it relied on something the old server had that the new one does not, you know why this matters.

Keep credentials for the domain registrar separate from hosting login

If your domain and hosting are with the same provider and that provider locks you out, you lose both at once. Registering the domain elsewhere means you can point it at a new host even if the original account is inaccessible. Namecheap offers .com registration at 6.79 USD per year with the NEWCOM679 offer, the same price at renewal, and keeping that login separate from your hosting account means one failure does not cascade into two.

Set up external monitoring that alerts you when the site goes down

You should not learn your site is offline from a customer. A monitoring service that checks the site every few minutes and emails or texts you when it stops responding means you know about the outage as it happens, not hours later. UptimeRobot and others offer this for free. The value is not in knowing the site is down—you will figure that out—but in knowing the moment it happens, which is when you still have options.

The providers in this article