HTTP Header Checker
Inspect a URL's HTTP/HTTPS response headers, redirect chain, and security configuration
Usage
• URL: enter a full URL (e.g. https://example.com); a bare domain starts from http:// so a redirect to HTTPS can be observed
• Shows the redirect chain hop by hop and never auto-follows to an untrusted target
• Parses security and performance configuration such as HSTS / CSP / compression / CDN
About the HTTP Header Checker
The HTTP header checker sends one real request to the target URL and returns every response header the server sends, the full redirect chain, and a parsed view of security headers (HSTS, CSP, X-Frame-Options) plus performance signals such as content compression and CDN usage.
Typical uses: confirm a site forces HTTP to HTTPS, verify that security headers are present, diagnose excessive or unexpected redirects, and check whether compression and a CDN are in place. The check runs server-side and re-validates each hop, so it never auto-follows to an untrusted target.
FAQ
What does the HTTP header checker show?
The status code, full redirect chain, and basic headers like Server, along with Strict-Transport-Security (HSTS), Content-Security-Policy (CSP), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, plus Content-Encoding compression and CDN signals.
Why does it say HTTP is not redirected to HTTPS?
It means that starting from http://, the whole redirect chain never lands on https://. Configure a forced HTTP-to-HTTPS redirect on your server or CDN and enable HSTS to improve transport security.
Does a missing HSTS or CSP matter?
HSTS lets browsers connect over HTTPS directly on later visits, lowering downgrade risk; CSP mitigates XSS and injection. Both are recommended; this tool flags whether they are set, and CSP is shown for reference only and does not count toward the optimization check.
Why does it report no compression or no CDN?
Missing headers mean this response lacks recognizable compression or CDN evidence. CDNs can hide identifiers and compression depends on content type and request headers. Check origin and edge configuration; a CDN does not automatically guarantee secure settings.
References and result limitations
Online results reflect the queried source or probe state at that time. Record the target, time, nodes or data source, and parameters when citing them. A single result does not establish continuous availability everywhere.
These references explain protocol or format rules; they do not endorse results produced by this site.