Your website isn't loading. You hit refresh. Still nothing. Before you panic and call your host at midnight — first figure out whether it's down for everyone or just you. The answer changes everything about what you do next.
How to Check if a Website Is Down for Everyone
The fastest way: use a website down checker tool. These services request your URL from their own servers — completely separate from your network, your browser, your ISP — and tell you what they see.
The most common ones:
- downforeveryoneorjustme.com — simplest, one URL, instant result
- isitdownrightnow.com — shows response time history alongside the status
- ping.tools — checks from multiple locations worldwide
- host-tracker.com — tests from different countries simultaneously
Enter your URL, run the check. Two outcomes:
| Result | What it means | What to do |
|---|---|---|
| "It's just you" | Your server is responding normally — the problem is on your end | Fix your local connection (see below) |
| "It's not just you" | Your server isn't responding to outside requests | Check your hosting, DNS, SSL, or domain |
If It's Down Just for You
Your server is fine. Something between you and the server is broken. Work through these in order:
1. Clear your browser cache
Your browser may be serving a cached error page. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to hard reload. Or open the URL in an incognito/private window — that skips the cache entirely.
2. Try a different browser
If Chrome can't load it but Firefox can, you have a browser-specific issue — usually a bad extension or corrupted cache. If neither loads it, keep going.
3. Flush your DNS cache
Your computer stores DNS lookups locally. If a site recently changed its DNS records, you may still be pointing at the old IP address. On Windows: open Command Prompt and run ipconfig /flushdns. On Mac: sudo dscacheutil -flushcache.
4. Try a different network
Switch to mobile data and try again. If it works on mobile, your home internet or ISP is blocking or routing the request incorrectly — not the website.
5. Check your hosts file
Your system has a local hosts file that can override DNS. If someone edited it — a developer testing something, a piece of malware — it can make a site unreachable just for you. On Windows: C:\Windows\System32\drivers\etc\hosts. On Mac/Linux: /etc/hosts.
If It's Down for Everyone
Your server isn't responding to the outside world. This is the serious scenario. Here's what's likely causing it and how to diagnose it fast.
Server is down or overloaded
Log into your hosting control panel (cPanel, Plesk, or your host's dashboard) and check the server status. Look for memory usage, CPU spikes, or error logs. A crashed PHP process, a runaway script, or a traffic spike can take down a shared hosting account entirely.
DNS failure
Your domain may not be pointing to your server correctly. Run a DNS lookup at dnschecker.org — enter your domain and check if all locations return the correct IP address. If DNS is failing globally, your site is unreachable regardless of whether the server is running fine.
Domain expired
An expired domain kills your website instantly — DNS stops resolving, email stops working, everything goes offline simultaneously. Check your registrar login and look at the expiry date. For what happens next and how long you have to recover it, see What Happens When Your Domain Expires.
SSL certificate error blocking the site
If your SSL certificate expired, browsers block visitors with a full-page security warning before they can see your site. This doesn't show as a traditional "down" state — the server responds, but the response is rejected. Use an online SSL checker to verify your certificate is valid. SSL Certificate Expiry: What Happens When It Expires covers the fix step by step.
Your host has an outage
Check your hosting provider's status page — most major hosts maintain one at status.[hostname].com. Also check social media and sites like Downdetector for reports from other customers. If it's a host-wide outage, there's nothing you can do except wait — but knowing this stops you from wasting hours investigating your own setup.
How to Stop Finding Out Late
A manual check tells you the current state. It can't tell you how long the site was down before you checked, or alert you when it happens at 3am.
The right answer is automated uptime monitoring — a tool that checks your site every 1–5 minutes from multiple locations and sends you an alert the moment it fails to respond. You find out in minutes, not hours.
What good uptime monitoring catches that manual checks miss:
- Outages that happen overnight or during weekends
- Intermittent failures that self-resolve before you check manually
- SSL certificates approaching expiry
- Domain expiry dates creeping up
- Slow response times that signal a problem before a full outage
The monitoring tool acts as your always-on website down checker — running every few minutes, from multiple countries, so you always know the status without having to ask.
For a full breakdown of what to look for in a monitoring tool, see What Is Uptime Monitoring? A Guide for Businesses.
- Use a website down checker — is it just you or everyone?
- If just you: clear cache → flush DNS → try another network
- If everyone: check hosting panel → check DNS → check domain expiry → check SSL → check host status page
- Set up uptime monitoring so you never run this checklist reactively again