Web
HTTP Header Checker
Inspect the final HTTP response headers without exposing cookies.
When to use this http header checker
Look at HTTP response headers when debugging caching, content types or proxy behavior. Headers here come from the final server response after HTTP redirects.
What to look for
- Compare Content-Type with the resource you expected to receive.
- Review Cache-Control and other cache headers alongside your CDN configuration.
- Repeat checks for affected paths; different resources can return different headers.
How to read the results
Headers describe the response returned to our server. Cookies and authentication challenge values are omitted.
PASS marks a stated check that passed. WARNING deserves review. FAIL marks a failed check. INFORMATION reports a fact. Results are a snapshot from our server, not a score or certification.
Why do these headers differ from my browser?
Servers can vary responses by request headers, cookies, location and cached content. This service sends its own unauthenticated request and omits cookie and authentication challenge values from results.
Download your results as Markdown to save the observations or discuss them with your AI assistant. Reports include the check timestamp and limitations.
CSP unsafe-inline: review the policy before removing it →
Redirect loops: find the repeating hop before changing rules →