Website Down Checker: Is the site down or just not working for you?

Enter the domain or URL above and click “Check”. Our server fetches the site live: it resolves the domain via DNS, establishes a connection (including certificate validation for HTTPS), follows redirects and evaluates the HTTP status code. If the server responds in time with a 2xx or 3xx code, the site is online. If any step fails or returns a 5xx error, the site is considered offline and you'll see the cause.

The checker fetches the site from our server, independently of your device and connection. If it reports “Online” but the site doesn't load for you, the problem is most likely on your end: an outdated DNS cache, your browser cache, your internet provider, a VPN or a firewall. Try opening the site over mobile data too. If it reports “Offline”, the site can't be reached from our server either, so the problem is most likely with the website itself. Each check is a snapshot from one location; timings may differ for visitors in other regions.

The server is running and responds, but returns a 4xx status code: 404 means the page doesn't exist, 403 denies access, 401 requires a login and 429 limits excessive requests. For 401, 403 and 429, the checker notes that bot protection or a login requirement may block the check even though the site works for regular visitors. In this case, the website itself isn't down.

All four are server errors and count as downtime. 500 is an internal application error. 502 (Bad Gateway) means the web server isn't getting a valid response from an underlying service such as PHP-FPM or Node. 503 indicates overload or maintenance. 504 (Gateway Timeout) means the underlying service is taking too long. If the server includes a Retry-After header with a 503 response, the checker points to maintenance. Next, check your server's error logs and resource usage.

A timeout means the server does not respond at all, perhaps because it is down or overloaded, or because a firewall is dropping packets. “Connection refused” means the server is reachable, but no web server is listening on the port—for example, because nginx or Apache is not running. Use the Port Checker to check specific ports.

A reachable site is marked as slow if the server takes at least 3 seconds to respond or the entire request, including DNS and redirects, takes at least 5 seconds. Timings are measured from our server and may differ for visitors in other regions.

If you enter only a domain, the checker tries https:// first. If that fails due to an expired or incorrect certificate or a closed port 443, it tries http:// and lets you know. Visitors using an https address will see a browser warning or error in that case. Use the SSL Checker to find out what's wrong with the certificate.

Yes. Enter the full URL, for example https://example.com/shop. The checker follows up to 8 redirects, checks the destination URL and displays it along with the number of redirects. If a page redirects in a loop or too many times, it reports a redirect loop or too many redirects. You can see every step in the chain in the Redirect Checker.

Yes, you don't need an account or a login. To prevent misuse, checks are limited per IP address and per website checked, and you'll need to wait a few seconds between checks. The checker provides a snapshot. If you want automatic notifications when a site goes down, use our server monitoring.