Logo Website Checker

How to Check If a Website Is Down (And What the Results Mean)

This guide walks through real‑world situations where a site appears “down”, how to use the Website Checker tool step by step, and how to turn the result (DNS, HTTP code, SSL, timing) into a concrete next action.

1. Quick checklist when a site won’t load

  1. Open the site in a different browser or device if you can (mobile vs desktop, Wi‑Fi vs mobile data).
  2. Run a check on the homepage URL in Website Checker.
  3. Note three things from the result: overall status, HTTP status code, and Domain / DNS status.
  4. Use the explanations below to decide whether the problem is DNS, the web server, SSL, or your own connection.

2. Reading the main status

When you run a check, you’ll see a label such as Online, Offline, Error, Online but Limited, or a domain‑focused status like Domain Not Found. These are summaries built from DNS and HTTP behaviour:

  • Online - DNS works and the server responded with a success code (usually 200).
  • Offline / Error - we couldn’t get a valid response (DNS failure, timeout, or connection error).
  • Online but Limited - the server is up, but bot protection or rate limiting blocked a full response.
  • Domain Exists (No Website) - DNS resolves, but there’s no usable web content yet (often on new setups).
  • Domain Not Found - the domain doesn’t currently resolve via public DNS.

3. Common scenarios and what to do next

A. New domain or DNS change

If you recently registered a domain, changed nameservers, or updated A/AAAA records and the checker shows Domain Not Found or only partial DNS data, you’re likely hitting DNS propagation delays.

  • Double‑check that your DNS records are correct at your registrar or DNS provider.
  • Wait 5-15 minutes and re‑run the check; global propagation can take longer depending on TTL settings.
  • If the domain has been active for a long time and suddenly stops resolving, verify that the domain hasn’t expired and that nameservers weren’t changed or removed.

B. DNS works, but the site is failing

When the checker shows a valid domain status but an HTTP code like 500, 502, or 503, the problem is usually on the web server or application layer:

  • 500 / 503 - application or server error (misconfigured app, resource limits, or temporary outage).
  • 502 - bad gateway between a reverse proxy (like Nginx, Apache, or a load balancer) and the upstream app.
  • Very high response time - the server is overloaded or slow to respond even when it succeeds.

If you manage the site, check your hosting control panel or server logs around the time of the failure. If you don’t, share the checker result (status + HTTP code + timing) with the site owner or hosting support to speed up diagnosis.

C. SSL / HTTPS issues

If the checker shows notes about SSL being insecure or misconfigured, you might see browser warnings like “connection not private” or “certificate not valid”. Typical causes include:

  • Expired certificate (common on sites that don’t auto‑renew Let’s Encrypt or similar).
  • Certificate issued for a different hostname (e.g. www.example.com vs example.com).
  • Mixed HTTP/HTTPS redirects that confuse browsers and tools.

The fix is usually to renew or re‑issue the certificate for the exact hostname and ensure your redirects send all traffic consistently to the HTTPS version.

D. Bot protection and “Online but Limited”

Some sites use services like Cloudflare or custom firewalls that challenge automated requests. In those cases:

  • The checker can confirm the server is online and responding.
  • We may not be able to fetch the full HTML or metadata; you’ll see “Online but Limited” with a note about protection.
  • In a browser, you might see a short delay or a challenge page that a human can solve but automated tools cannot.

If this is your site and legitimate bots (API clients, uptime monitors) are being blocked, adjust your security settings or allowlist known IPs as appropriate.

4. Understanding HTTP status codes (quick reference)

Every HTTP response includes a numeric status code. Here’s a quick reference focused on troubleshooting:

  • 200 OK - The site is up and returned the requested page or resource.
  • 301 / 302 Redirect - The URL redirects somewhere else; the checker follows the chain and shows the final URL.
  • 404 Not Found - The site is online, but that specific path doesn’t exist (check for typos or moved pages).
  • 403 Forbidden - The server refused the request (permissions or bot protection).
  • 429 Too Many Requests - Rate limiting; slow down or reduce automated checks.
  • 500 / 502 / 503 - Server‑side issues; investigate logs or contact your hosting provider.

5. Using the result in support conversations

When you talk to a hosting provider, developer, or ISP support, a screenshot or copy of the checker result is often more useful than “it doesn’t work”. Include:

  • The URL you tested.
  • The overall status and HTTP code.
  • The response time and whether SSL is marked as secure or insecure.
  • Any notes shown about DNS, redirects, or bot protection.

Use the checker · FAQ · About