HTTP status checker

Enter any URL and we will request it from our server, then show you the HTTP status code, the full redirect chain, the response time and the final URL. The fastest way to confirm whether your website is up or down.

How the HTTP status checker works

When you submit a URL, our server sends a single HTTP GET request to it, exactly like a browser would. We follow up to five redirects and measure the total time until the final response arrives.

The status code is the most important part of the answer. A code in the 200 range means success, a 300 code means a redirect, a 400 code means the request was rejected, and a 500 code means the server failed. We also show the Server header so you can see what software is behind the site.

The check runs from our infrastructure, not from your own network. That is useful because it tells you whether the site is reachable from the public internet, not just from your computer or office. If the tool reports the site is up but you cannot reach it, the problem is most likely local (your DNS, firewall or ISP).

How to read the result

The colour of the status badge tells you the category at a glance. Here is what each class means:

• 2xx (green) - success. The page loaded correctly.
• 3xx (blue) - redirect. The URL points somewhere else; check the final URL.
• 4xx (amber) - client error such as 404 Not Found or 403 Forbidden. The server works but rejected this request.
• 5xx (red) - server error such as 502 Bad Gateway or 503 Service Unavailable. The site is down for visitors.

Common problems this tool helps diagnose

My site shows 503 or 502. A 5xx code points to a server-side fault: an overloaded backend, a crashed application or a failing reverse proxy. The page is unreachable for everyone, so fix it as a priority.

Too many redirects or a redirect loop. If the redirect chain is long or never reaches a 200, you likely have a misconfigured HTTPS or www redirect. Long chains also slow down page loads and hurt SEO.

The tool says up but I see an error. If we report 200 OK but your browser shows an error, the issue is usually local: stale DNS cache, a VPN, a firewall rule or an ISP outage. Try from a different network or device.

Frequently asked questions