HTTP Status Code Checker
Quick HTTP status code check for any URL — follows redirects and shows response time.
About HTTP Status
Returns the HTTP status code for any URL — a fast, single-purpose check when you just need to know if a page is returning 200, 404, 500, or something else. Useful for quickly confirming a page is reachable after a deploy, or checking that a maintenance or custom error page is returning the correct status code — a surprisingly common miss, since a "not found" page that actually returns 200 is invisible to monitoring tools and search engines alike.
The check follows redirects (up to 10) and reports the final URL's status, along with how many redirects it passed through; to see each hop with its own code, use the Redirect Tracer.
Common Codes
301 Moved Permanently
302 Found (temp redirect)
304 Not Modified
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
429 Rate Limited
500 Server Error
503 Unavailable
Related Tools
What the result shows
The tool sends a HEAD request, follows up to 10 redirects and reports the status code of the final URL, together with the final address, the number of redirects followed and the total response time. To see every hop and its own code, use the Redirect Tracer.
Status code classes
- 2xx — success. 200 OK is the normal answer; 204 means success with no body.
- 3xx — redirect. 301/308 are permanent, 302/307 temporary, 304 means "not modified" for a cached copy.
- 4xx — client error. 401 needs authentication, 403 is refused, 404 not found, 410 gone for good, 429 rate limited.
- 5xx — server error. 500 is an application failure, 502 and 504 mean a proxy or load balancer could not get an answer from the backend, 503 means overloaded or in maintenance.
Common surprises
- 405 or 403 here, but the page opens in a browser: some servers and firewalls reject HEAD requests or unknown user agents. Check with
curl -sI https://example.com/and with a normal GET:curl -s -o /dev/null -w "%{http_code}" https://example.com/. - A "not found" page that returns 200: called a soft 404. Search engines may index it and monitoring won't alert. Configure the error page to return 404.
- Maintenance page: it should return 503, ideally with a
Retry-Afterheader, so search engines keep the old copy instead of indexing the maintenance text. - Cloudflare 52x codes: 521 origin down, 522 connection timed out, 523 origin unreachable, 525/526 TLS problems between Cloudflare and the origin. Check the origin's certificate with the SSL Checker.