Website health

Is my website down, or is it just me?

By Purlock · Updated 3 min read

The short answer

Check from somewhere other than your own network: open the site on your phone using mobile data, or run an outside check like Purlock's website health check. If it loads elsewhere, the problem is your connection, browser or DNS cache. If it fails everywhere, the error message tells you where to look: a DNS error points at your domain, a certificate warning at SSL, and a 500 or 503 at your host or code.

Key points

  • Test from outside your own network before assuming the site is down.
  • The exact error tells you which layer failed: domain, certificate, server or code.
  • An expired domain or certificate is a common cause, and both are easy to rule out.

How can I tell if a website is down for everyone?

  1. Open the site on your phone with Wi-Fi turned off. If it loads, the problem is on your network or computer.
  2. Try a private window, which ignores your browser's cache and extensions.
  3. Run an outside check, such as the website health check, which loads your site from Purlock's servers and reports what it got back.
  4. Check your host's status page. Most hosts publish one, and an outage there explains everything.

Website health check

SSL and domain expiry, DNS, https redirects and security headers.

Try it free

What do website error messages mean?

Common website errors and where to look
What you seeWhat it usually meansWhere to look
This site can't be reached / DNS_PROBEThe domain doesn't point anywhereDomain registrar and DNS records
Your connection is not privateThe SSL certificate expired or doesn't matchYour host's SSL settings
500 Internal Server ErrorThe site's code crashedYour host's error logs
502 Bad Gateway / 504 Gateway TimeoutA server behind the host didn't answer in timeHost status page, app server
503 Service UnavailableOverloaded or in maintenanceHost status page, plan limits
404 Not Found on the homepageThe site was moved or the deploy is emptyYour last deploy
Too many redirectsA redirect loop, often http and https fightingRedirect and SSL settings

Why would my website suddenly go down?

  • The domain expired, often because the card on file at the registrar expired.
  • The SSL certificate didn't renew after a DNS or hosting change.
  • A deploy or plugin update broke the code.
  • Your hosting plan hit a limit, or a payment failed.
  • DNS records were changed or deleted while moving email or another service.
  • Your host is having an outage.

How do I get alerted when my website goes down?

Turn a check into a monitor. Purlock's website health monitor checks your site and emails you when it stops answering, and 30, 14 and 7 days before your certificate or domain expires, so the two most common outages never happen in the first place.

For minute by minute uptime alerts, a dedicated uptime service is the right tool. The two complement each other: uptime tells you it's down now, a health monitor tells you what's about to break.

More questions

Why does my site work for me but not for others?
Your browser or network may have an old copy cached, or your DNS may still point at an old server. Visitors with fresh DNS see the new, broken state. Check from mobile data or an outside tool.
Why does my site work for others but not for me?
Usually a stale DNS cache, a browser extension, a VPN or a firewall on your network. Try a private window and another network.
How long does DNS take to update?
Usually minutes to a few hours, depending on the TTL set on the record. Some networks hold old answers longer.