
A website will not load and you are not sure whether the problem is the site, your connection or something in between. Before you call your web host or panic about lost sales, a few quick checks will tell you what is going on. This guide shows how to check if a website is down for everyone or just for you, and what to do in each case.
Step 1: Check whether it is just you
Start with the simplest tests:
- Try another website. If nothing loads, the problem is your internet connection, not the site.
- Try another device or network. Open the site on your phone using mobile data instead of Wi-Fi.
- Use an uptime checker. Enter the address in our free website uptime checker. It checks the site from our server, so you can see whether it responds from outside your network.
If the site works elsewhere but not for you, it is a local problem. If it fails everywhere, the site itself is down.
If the website is down only for you
Work through these fixes in order:
- Refresh without the cache. Press Ctrl+F5 on Windows or Cmd+Shift+R on a Mac to reload the page fresh.
- Try a private window. This rules out browser extensions and stored cookies.
- Restart your router and reconnect.
- Check for a recent DNS change. If the site recently moved to a new host or domain settings changed, some networks may still be using old information. Our DNS propagation checker shows what different parts of the world are seeing.
- Check whether your IP is blocked. Security firewalls sometimes block an IP address after repeated failed logins. Find your address with What Is My IP and share it with the site owner or host.
If the website is down for everyone
If you own the site, these checks help you find the cause quickly:
1. Has the domain expired?
An expired domain is one of the most common and most avoidable causes of downtime. Check the expiry date with a WHOIS lookup and renew immediately if needed.
2. Are the DNS records correct?
DNS connects your domain name to your server. If records were changed or deleted, visitors cannot reach the site. Use the DNS lookup to see where your domain currently points.
3. Has the SSL certificate expired?
If the site loads with a security warning, the SSL certificate may have expired or been set up incorrectly. Browsers warn visitors away from these sites. Test it with the SSL checker.
4. What does the server return?
Error codes tell you a lot. Check them with the HTTP headers checker:
| Code | What it usually means |
|---|---|
| 500 | An error on the server, often a broken plugin, theme or code change |
| 502 or 504 | The server or a service behind it is not responding in time |
| 503 | The server is overloaded or in maintenance mode |
| 403 | Access is blocked, often by a firewall or file permissions |
| 404 | The page does not exist, but the site itself is up |
5. Contact your host
If you cannot find the cause, contact your hosting provider with the error message, the time it started and any recent changes you made. Recent updates, new plugins and DNS changes are the first things they will ask about.
How to catch downtime early
- Set your domain and hosting to renew automatically
- Use a monitoring service that alerts you when the site goes down
- Keep regular backups so you can restore quickly
- Make changes on a staging copy before applying them to the live site
If your site goes down often or loads slowly, a website SEO audit and page speed check are good places to start. For hands-on help, Sayf & Co.'s website team can take care of it.