Practical guide
How to use the http headers checker
The HTTP headers checker retrieves a public URL and lists response headers returned to the request. Headers reveal status, caching, content type, security policy, redirects and infrastructure details that are not visible in the page body.
Good reasons to use it
- Verify cache-control, content-type and redirect headers.
- Check whether security headers are present after a configuration change.
- Compare CDN output with expected origin behavior.
A reliable workflow
- Enter a complete public URL.
- Review status and headers for conflicts, missing values or unexpected intermediaries.
- Confirm at the origin and in a browser developer panel before changing policy.
How to interpret the result
Headers can vary by method, user agent, authentication, location, cookies and cache state. Presence alone does not prove a secure implementation; policy values must be correct for the application.
Frequently asked questions
Why are server headers different through a CDN?
The CDN may add, remove or rewrite headers and can serve a cached response without contacting the origin.
Which header prevents indexing?
An X-Robots-Tag containing noindex can instruct supporting search engines not to index the response.