HTTP Headers Checker
Inspect actual target response headers and understand caching and security controls.
Inspect a public website
Analyze URL sends the submitted URL, including its query parameters, to the WebToolspire API. The API checks public DNS and requests the target without your browser cookies or authorization. Do not submit secret URLs.
One URL, an eight-second server deadline, and at most five redirects. Only response headers are inspected; bodies are cancelled.
Understand your results
For maintainers understanding target response headers and browser policies.
The report contains only selected headers returned by the public target after safe redirects. Caching identifiers and policy headers have context-specific roles. Missing optional headers are distinguished from review recommendations; absence alone does not establish a vulnerability.
How to use this tool
- Submit a public website URL and run the analysis.
- Inspect the target HTTP status, final URL, actual header values, and explanations.
- Copy the report to discuss any policy changes with the application maintainer before deploying them.
What the observations mean
Values come from the target response, not this site’s own response headers. Selected fields include caching, content type, indexing directives, and security-related headers. A review label is contextual advice rather than a complete security assessment.
Worked example
Review why a publicly reachable page might still request exclusion from search.
Possible response headers:
Content-Type: text/html
X-Robots-Tag: noindex
Cache-Control: max-age=300If these headers are returned, the report exposes noindex separately from the cache lifetime and content type. An HTTP 200 response by itself does not establish indexability.
Limits and processing
Requires the API and observes selected actual GET response headers; it does not run a browser or certify security, caching correctness or indexing. Response bodies are cancelled after headers for this operation.
Common problems and practical fixes
- Unexpected noindex
- Investigate X-Robots-Tag at the host or CDN layer; an HTML editor may not control it.
- Cache policy differs
- Compare the response with your intended public/private caching behavior and confirm intermediary configuration.
- Missing optional header
- Review whether it is appropriate to this response before adding a blanket policy.
Best practices
Inspect real browser requests as well: variants, cookies, geographic routing, and authentication can produce different headers. Cookie values are not returned by this tool.
Practical tips
- CSP frame-ancestors can replace the framing protection otherwise associated with X-Frame-Options.
- HSTS matters on HTTPS sites and should be deployed deliberately.
- No browser cookies or Authorization headers are forwarded, so authenticated responses are outside this check.
Frequently asked questions
Practical answers for using the HTTP Headers Checker.
Are these the API’s own headers?
No. The report reads the fetched target response. API CORS and other service headers are not presented as target headers.
Why are some missing headers informational?
ETag, Expires, Server and other optional headers are not universally required. Their usefulness depends on the resource and caching strategy.
Is this a complete security audit?
No. It describes public response headers, not application behavior, authentication, vulnerabilities, or exploitation resistance.