How to Check if a Website is Down

There's nothing more frustrating than trying to access a website only to be met with a blank page, spinning loader, or cryptic error message. Before you start troubleshooting your entire network or calling your ISP, you need to answer one critical question: Is the website down for everyone, or is it just me?

This guide covers seven proven methods to check website status—from quick online tools anyone can use to command-line techniques for developers and IT professionals.

Method 1: Use an Online Status Checker (Fastest)

The quickest way to check if a website is down is to use a third-party status checker. These tools test the website from multiple locations around the world, giving you an immediate answer.

Pro tip: Look for spikes in user reports, not just the current status. A sudden spike in the last 15 minutes usually indicates a real outage, while scattered reports throughout the day might be individual connection issues.

Method 2: Try a Different Network

Sometimes the issue is specific to your ISP or local network. The simplest test is to disconnect from Wi-Fi and try loading the website on mobile data (or vice versa).

Method 3: Ping the Website

The ping command sends packets to a server and measures whether it responds. This tells you if the server is reachable at the network level, even if the website itself isn't loading.

How to interpret ping results:

• Successful replies — The server is reachable; the issue may be with the web application, not the server itself
• "Request timeout" — The server isn't responding; it may be down or blocking ICMP packets
• "Unknown host" — DNS can't resolve the domain; could be a DNS issue or the domain doesn't exist

Method 4: Use Curl to Check HTTP Status

For developers and power users, curl provides more detailed information than ping. It actually makes an HTTP request and shows you the server's response code.

Common HTTP status codes:

• 200 — OK (website is working)
• 301/302 — Redirect (website is working but forwarding you)
• 403 — Forbidden (server is up but blocking access)
• 404 — Not Found (specific page missing, but server works)
• 500 — Internal Server Error (server-side problem)
• 502 — Bad Gateway (proxy or load balancer issue)
• 503 — Service Unavailable (server overloaded or in maintenance)
• 504 — Gateway Timeout (upstream server not responding)

Method 5: Check Browser Developer Tools

Your browser's built-in developer tools can reveal exactly why a page isn't loading. This is especially useful for diagnosing partial outages where some elements load but others don't.

The Console tab may also show JavaScript errors or failed API calls that explain why the page isn't working properly.

Method 6: Try a Different Browser or Incognito Mode

Browser extensions, cached data, or corrupted cookies can prevent websites from loading correctly. Testing in incognito/private mode eliminates these variables.

• Chrome: Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac)
• Firefox: Ctrl+Shift+P or Cmd+Shift+P
• Safari: Cmd+Shift+N
• Edge: Ctrl+Shift+N

If the site works in incognito mode, the issue is likely a browser extension or cached data. Try disabling extensions one by one to find the culprit.

Method 7: Check DNS Resolution

DNS (Domain Name System) translates domain names into IP addresses. If DNS isn't working, your browser can't find the server even if it's online.

If DNS resolution fails, try using a public DNS server like Google (8.8.8.8) or Cloudflare (1.1.1.1) instead of your ISP's DNS.

Common Causes of Website Downtime

Understanding why websites go down helps you troubleshoot faster and set appropriate expectations for when they'll recover.

Check Popular Services Right Now

Looking for the status of a specific service? Check these popular status pages:

View all 100+ monitored services →

Frequently Asked Questions