200 · 301 · 302 · 404 · 5xx · headers

HTTP Status Checker

See the status code of any URL, follow its redirect chain hop by hop, and review the response headers and security headers.

Try http://github.com, http://www.sslverify.net or a 404.

How it works

Full redirect chain

Every hop with its status code, Location header, server IP, HTTP version and response time, up to 10 redirects. Loops are detected.

Response headers

All headers of the final response, plus a quick check of HSTS, Content-Security-Policy, X-Frame-Options and other security headers.

Real TLS validation

HTTPS hops are validated like a browser would. Expired, self-signed or mismatched certificates show up as errors instead of being skipped.

Questions

What's the difference between 301, 302, 307 and 308?

301 and 308 are permanent: search engines move ranking to the new URL. 302 and 307 are temporary. 307 and 308 also guarantee the request method stays the same (a POST stays a POST), while 301/302 may turn it into a GET.

How many redirects are too many?

Ideally one: http://example.com → https://example.com/. Every extra hop adds a round trip for visitors and wastes crawl budget. Chains like http → https → www → trailing slash are worth collapsing into a single redirect.

Why does a page return 403 here but work in my browser?

Some sites block non-browser clients, data-center IPs or requests without cookies, often through a WAF or bot protection. The checker identifies itself honestly and doesn't run JavaScript challenges.

Which security headers should every site have?

At minimum Strict-Transport-Security (HSTS), X-Content-Type-Options: nosniff, a framing policy (X-Frame-Options or CSP frame-ancestors) and a Referrer-Policy. A Content-Security-Policy is the strongest defense against XSS but needs tuning per site.

More free tools