How to Check If a Website Is Down: Tools and Methods

You've just tried to visit a website and it won't load. Before you spend an hour debugging, the first question to answer is simple: is the website actually down, or is it just down for you?

This guide covers every practical method for checking whether a website is offline — from instant online tools to command-line diagnostics — and explains what to do next depending on what you find.

Is It Down for Everyone or Just Me?

The most common scenario when a site won't load is that it's actually accessible globally but something in your local setup is causing it to fail. Before assuming the site is down, rule out these local causes:

• Your internet connection — try loading a different website first
• Your browser cache — try a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac)
• DNS cache — your computer may have cached a bad DNS record
• Browser extensions — an ad blocker or VPN extension may be interfering
• Your ISP — regional routing issues can affect specific sites

The fastest way to answer the "just me?" question is to use an external checker.

Method 1: Use an Online Website Down Checker

An online website down checker tests whether your target URL is accessible from an independent server — completely separate from your network. If the checker says the site is up, the problem is local to you. If it says the site is down, it's a real outage.

Popular options include:

• Domain Monitor's free check tool at domain-monitor.io
• downforeveryoneorjustme.com — simple pass/fail check
• isitdownrightnow.com — checks from multiple locations

These tools work by sending an HTTP request to the URL and reporting whether they received a valid response. Most also show the HTTP status code and response time.

Method 2: Ping the Server

The ping command sends ICMP packets to a server and checks for a response. It tests basic network connectivity — whether the server's IP address is reachable — rather than HTTP availability.

Windows:

ping yourdomain.com

Mac/Linux:

ping -c 4 yourdomain.com

If you get replies, the server is reachable at the network level. If you get timeouts or "request timed out", either the server is down or ICMP is blocked by the server's firewall (common on cloud providers).

Note that a successful ping doesn't mean the website is up — just that the server's IP is responding to network pings. A web server can be running but serving errors.

Method 3: Use curl to Check the HTTP Response

curl gives you more detail than a simple ping — it shows the actual HTTP response code.

curl -I https://yourdomain.com

The -I flag requests only the headers. Look for:

• HTTP/2 200 — site is up and responding normally
• HTTP/2 503 — server is responding but unavailable (often maintenance mode)
• HTTP/2 404 — the page doesn't exist
• Connection refused or timeout — server isn't responding

This method is available on Mac, Linux, and Windows (with recent versions of Windows 10/11).

Method 4: Run a Traceroute

If ping fails, a traceroute can show you where the connection breaks down. Each "hop" represents a router between you and the destination.

Windows:

tracert yourdomain.com

Mac/Linux:

traceroute yourdomain.com

If the trace stops at a particular hop, that's where the connection is failing. If it stops close to the destination server (the last few hops), the problem is likely with the server or its hosting provider. If it stops early, the issue is more likely with your ISP or a network in between.

Method 5: Check DNS Resolution

Sometimes a website appears down because DNS isn't resolving the domain correctly. You can test this with nslookup:

Windows/Mac/Linux:

nslookup yourdomain.com

If this returns a valid IP address, DNS is working. If it returns an error or can't find the host, the problem is DNS-related — which could mean a domain expiry, a DNS misconfiguration, or a DNS propagation delay after a recent change.

What the HTTP Status Codes Mean

When a website is "down", the specific HTTP response code tells you what kind of problem it is:

See HTTP status codes for a complete reference.

What to Do If the Site Is Down

If you've confirmed the site is actually down (not just a local issue), your next steps depend on whether you own the site:

If you own the site:

1. Check your hosting provider's status page for known incidents
2. Log in to your server and check application and web server logs
3. Check if your domain is still active (WHOIS lookup)
4. Verify your SSL certificate hasn't expired
5. Check that your database is running

If you don't own the site:

1. Check the site's official status page (usually status.sitename.com)
2. Check the site's social media for outage announcements
3. Try again in 15-30 minutes — most outages are short-lived

Prevent Future Downtime Discovery via Monitoring

The reactive approach — noticing a site is down and then diagnosing it — is far slower than being alerted automatically when it happens.

Website uptime monitoring checks your site continuously and sends you an alert the moment it goes down. Rather than discovering downtime when a user complains or you happen to visit your own site, you're notified within 60 seconds of the first failure.

Domain Monitor provides free uptime monitoring with instant email alerts — so the next time your site goes down, you'll know before any of your users do.

Never discover downtime the hard way — set up monitoring at Domain Monitor.

Related Articles

• "Check Website Availability Online: Tools and Methods"
• "Is My Website Down Right Now? How to Check and Fix It"
• "Website Down Checker: How to Check If Your Site Is Offline Right Now"