Website Down? The First Steps Before You Panic

A site that won't load is one of the more stressful things to deal with, especially if it's tied to your income. Before assuming the worst, it's worth spending five minutes on a short set of checks. Most of the time, they either fix the problem outright or tell you exactly what to say to support instead of just "it's down."

Check 1: Is it actually down, or just down for you

Open the site from your phone on mobile data instead of Wi-Fi, or ask someone else to check it from their own connection. A free third-party "is it down for everyone" checker works too. If the site loads fine elsewhere, the issue is local: your Wi-Fi, your ISP, a DNS cache on your device, or a browser extension. If it's genuinely unreachable from multiple networks and devices, move to the next check.

Check 2: What exactly does the error say

The specific error message matters more than "it's not working." A browser saying it can't find the server at all points toward DNS. A timeout after a long wait points toward the server itself. An actual page loading with an error message on it, like a database connection error or a critical error notice, means the server is up and WordPress is running, it's just failing partway through. Each of these has a different cause and a different fix.

• "This site can't be reached" or DNS-related wording: likely a domain or DNS issue
• A long wait followed by a timeout: likely a server or hosting issue
• A page loads with a specific error message on it: likely an application-level issue, not a server outage
• Only images or some page elements missing: likely a partial content issue, not the site being down

Check 3: Did anything change recently

Think back over the last day or two. A plugin or theme update, a DNS change, a new SSL certificate, or an edit to a configuration file are the most common triggers for a site suddenly going down. If you or someone on your team made a change right before the outage started, that's very likely connected, and knowing it saves significant diagnostic time, whether you're fixing it yourself or explaining it to support.

Check 4: Look at your domain, not just your hosting

A surprising number of "my site is down" situations turn out to be an expired domain registration or a DNS record that got changed unintentionally, rather than a hosting problem at all. Log into your domain registrar and confirm the domain hasn't lapsed, and check that its DNS records still point where they're supposed to. This takes two minutes and rules out an entire category of causes.

Check 5: Check your hosting provider's status page

Most hosting providers maintain a status page showing current incidents across their infrastructure. If there's a known issue already posted there, you have your answer, and a timeline for when it's expected to resolve, without needing to open a support ticket at all. If nothing is posted, that's useful information too: it likely means the issue is specific to your account or site rather than a broader outage.

Check 6: Try the admin area separately from the front end

If you run WordPress, try loading yourdomain.com/wp-admin specifically. If the admin area loads while the public site doesn't, the problem is likely something specific to the front end, like a theme file or a caching issue, rather than the server itself being unreachable. If both are down with the same error, that points toward something lower-level, at the server or database.

Check 7: Look at whether the SSL certificate has expired

A browser showing a security warning instead of a normal page, rather than a fully broken connection, often means an SSL certificate has expired or failed to renew, rather than the site being down in any deeper sense. Most modern hosting includes automatic certificate renewal, but a recent domain or DNS change can occasionally interrupt that process. Check the certificate's expiration date directly through your browser's site information panel before assuming a more serious server problem is involved.

What not to do while you're still troubleshooting

It's tempting to start making changes immediately, restoring an old backup, switching themes, or contacting several people at once, before you've actually confirmed what's wrong. Making changes before you understand the cause can erase the evidence that would have explained it, and can occasionally make the underlying problem harder to diagnose rather than easier. Run through the checks above first, note what each one shows, and only then decide on a fix, rather than reaching for the most drastic option available.

• Avoid restoring a backup before confirming what actually broke
• Avoid changing multiple things at once, since it hides which change fixed it
• Write down what each check above showed, in case you need to explain it to support

What to have ready before contacting support

• The exact time the issue started, as precisely as you can pin it down
• The exact error message or behavior, word for word if possible
• Whether it affects the front end, the admin area, or both
• Anything that changed right before it started, even something that seems unrelated
• Confirmation of whether it's down from multiple devices and networks, or just one

Most outages resolve faster once you know which of these categories you're actually dealing with. A domain problem, a DNS problem, a server problem, and an application problem each need a completely different response, and five minutes of checking is almost always faster than guessing at the fix, or waiting anxiously for a reply with nothing but "my site is down" to go on.