How to Check If a Website Is Down: Tools and Methods
Learn how to check whether a website is down for everyone or just you, using browser tools, command-line utilities, online checkers, and automated monitoring.
Last updated: 2026-02-18
Is It Down for Everyone or Just You?
When a website does not load, the first question is whether the problem is on your end or theirs. A site can appear down to you while working perfectly for everyone else — and vice versa. The difference determines whether you need to troubleshoot your own network or wait for the site to recover.
There are several methods to answer this question, ranging from quick online checks to detailed command-line diagnostics.
Quick Checks First
Before reaching for tools, rule out the obvious.
Try a Different Browser
Open the site in a different browser (or an incognito/private window). If it loads, your primary browser's cache or extensions are likely the issue. Browser extensions, especially ad blockers and privacy tools, can block requests or modify DNS resolution.
Switch Networks
If you are on WiFi, try mobile data (or vice versa). If the site loads on one network but not the other, the problem is network-specific — likely your ISP's DNS resolver or a local firewall rule.
Try a Different Device
Load the site on your phone, a tablet, or another computer. If it works on a different device on the same network, the issue is specific to your machine (hosts file, local DNS cache, firewall software).
Method 1: Online "Is It Down" Checkers
The fastest way to check whether a site is down for everyone is to use a web-based tool that tests the site from a server outside your network.
These tools send an HTTP request to the target URL from their own servers and report whether they received a response. If the tool can reach the site but you cannot, the problem is on your end. If the tool also cannot reach it, the site is down for everyone.
Popular options include Down For Everyone Or Just Me, Is It Down Right Now, and similar services. Enter the URL, and you get an instant answer.
Online checkers test from a single location (or a small number of locations). A site can be down in one region but up in another due to CDN issues, DNS propagation differences, or regional server failures. For geographic accuracy, use a tool that tests from multiple locations.
Method 2: Command-Line Diagnostics
Command-line tools give you more detail about what is failing and where.
Ping tests whether the server's IP address is reachable:
ping example.com
If ping succeeds, the server is reachable at the network level. If it fails, the server may be down, or ICMP may be blocked (many servers disable ping responses). Ping alone is not definitive.
Curl sends an actual HTTP request and shows the response:
curl -I https://example.com
The -I flag fetches only headers. A 200 OK response means the site is up. A 5xx error means the server is responding but encountering an error. A connection timeout means the server is unreachable. A DNS resolution failure means the domain is not resolving.
Traceroute (or tracert on Windows) shows the network path to the server:
traceroute example.com
This reveals where packets are being dropped. If the trace completes to the destination but the site does not load, the issue is at the application level. If the trace stops at a hop along the way, there is a network-level routing problem.
Nslookup / Dig checks DNS resolution:
nslookup example.com
dig example.com A
If DNS does not resolve, the site appears down because the browser cannot find the server's IP address. This can mean the domain expired, DNS records were deleted, or the nameservers are unreachable.
Know When Your Site Goes Down — Before Users Do
Site Watcher monitors uptime from multiple locations and alerts you within minutes of a failure. Also covers SSL, DNS, domain expiry, and vendor dependencies. Free for 3 targets.
Method 3: Browser Developer Tools
Your browser's developer tools (F12 or Ctrl+Shift+I) provide diagnostic information without leaving the browser.
Open the Network tab and reload the page. The network panel shows every request the browser makes and the status of each one. Look for:
- ERR_NAME_NOT_RESOLVED — DNS lookup failed. The domain cannot be resolved to an IP address. This indicates a DNS issue: expired domain, deleted DNS records, or unreachable nameservers.
- ERR_CONNECTION_REFUSED — The server's IP was reached, but nothing is listening on port 80 or 443. The web server process (nginx, Apache) may have crashed or is not running.
- ERR_CONNECTION_TIMED_OUT — The browser waited for a connection but the server never responded. The server may be overwhelmed, firewalled, or completely offline.
- ERR_SSL_PROTOCOL_ERROR — The server is reachable but the SSL handshake failed. The certificate may be expired, misconfigured, or the TLS version is incompatible.
- 5xx status codes — The server is responding but returning errors. 502 (Bad Gateway) and 503 (Service Unavailable) are common during outages.
Method 4: Check from a Different Location
If you suspect the issue is regional, test from another geographic location.
Use a VPN. Connect to a VPN server in a different country or region and try loading the site. If it loads via VPN but not directly, the issue is specific to your network or region.
Ask someone else. A quick message to a colleague in a different location can confirm whether the site is globally down or just locally unreachable.
Use online browser tools. Services that render web pages from remote servers let you see exactly what a user in another country would see, including any error messages.
Common Causes: "Just Me" vs "Everyone"
| Cause | Down For | How to Fix |
|---|---|---|
| Stale DNS cache | Just you | Flush DNS: ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (macOS) |
| ISP DNS resolver issue | Your ISP's users | Switch to 8.8.8.8 or 1.1.1.1 in your network settings |
| Browser cache / extensions | Just you | Try incognito mode or a different browser |
| Hosts file override | Just you | Check /etc/hosts (Linux/macOS) or C:\Windows\System32\drivers\etc\hosts |
| Local firewall or antivirus | Just you | Temporarily disable and test; check firewall rules |
| IP-based block or rate limit | Just you | Try from a different IP; contact site owner if blocked in error |
| Server crash | Everyone | Site owner must restart services or wait for hosting provider |
| DNS misconfiguration | Everyone | Site owner must fix DNS records at their registrar/DNS provider |
| Expired domain | Everyone | Site owner must renew the domain registration |
| Expired SSL certificate | Everyone | Site owner must renew the SSL certificate |
| DDoS attack | Everyone | Site owner must engage DDoS mitigation or wait for attack to subside |
| Hosting provider outage | Everyone | Wait for the hosting provider to resolve; check their status page |
What to Do Once You Confirm the Site Is Down
If you are the site owner and your site is confirmed down for everyone:
Check Your Hosting Provider's Status Page
Before debugging, check if your hosting provider is experiencing an outage. If they are, your options are limited until they resolve it.
Verify DNS Resolution
Run dig yourdomain.com A to confirm your domain resolves correctly. If it does not, check your domain registration (is it expired?) and your DNS records (were they changed?).
Check SSL Certificate
If the site loads over HTTP but not HTTPS, or if you see SSL errors, your certificate may have expired. Run openssl s_client -connect yourdomain.com:443 to check.
Check Server Processes
If you have server access, check whether your web server (nginx, Apache) and application processes are running. Check server logs for error messages. Restart services if needed.
Communicate with Users
If the outage will take time to resolve, update your status page or social media. Users are more patient when they know you are aware of the problem and working on it.
Manual checks are useful for diagnosing an outage after you notice it. Automated monitoring catches outages the moment they happen — often before any user reports a problem. The difference between a 2-minute response time and a 2-hour response time is usually whether you had monitoring in place.
Why Automated Monitoring Beats Manual Checks
Instant Detection
Monitoring checks your site every 1-5 minutes from multiple locations. You are alerted within minutes of a failure, not hours later when a customer emails you.
Root Cause Clues
A monitoring tool that checks uptime, SSL, DNS, and domain health can often tell you why the site is down — not just that it is down. DNS resolution failure points to a DNS issue. SSL handshake failure points to a certificate issue.
Historical Data
Monitoring logs every check, giving you uptime statistics, response time trends, and incident history. This data helps you identify patterns and prevent future outages.
Multi-Location Verification
Monitoring from multiple geographic locations distinguishes between regional issues and global outages, reducing false alarms from single-location network problems.
Checking if a website is down is easy. Knowing the moment it goes down, before anyone else notices, requires monitoring.
Never Be the Last to Know Your Site Is Down
Site Watcher monitors uptime, SSL, DNS, domain expiry, and vendor dependencies from multiple locations. Get alerted the moment something breaks. $39/mo unlimited. Free for 3 targets.