HTTP Headers & Redirect Checker
Inspect the response status, selected useful HTTP headers, and redirect chain for a public HTTP or HTTPS URL.
What this result means
Headers and redirects are one request-path view. CDN behavior, cookies, authentication, method handling, and location can produce a different response for another visitor.
How this check works
Enter a full HTTP or HTTPS URL, or a hostname to use HTTPS by default. The checker follows a bounded number of redirects manually, validates each target before connecting, and reports the final status plus a small set of response headers useful for troubleshooting.
A redirect chain shows how this request moved between URLs. Redirect loops, too many redirects, unsupported schemes, private targets, and request failures are reported honestly instead of being followed indefinitely. HEAD is used first, with a small GET fallback for servers that do not support HEAD.
Security headers are context, not a standalone security grade. This checker does not display cookies or authorization data, does not submit forms, and does not make requests to private or reserved network addresses.