Cache Headers Analyzer
Understand cache policies. Compare evidence. Build careful, manual tests for web cache deception and poisoning—without turning a header signal into a vulnerability claim.
Collect a live response
GET or HEAD only. Origin-form requests use HTTPS. No request body; Host is derived and verified, not spoofed.
One request per test. Public HTTP(S) only; custom headers require HTTPS. No redirects or response bodies are fetched.
Response snapshot
Response headers will appear here, with cookie values redacted.
PoC generation prepares a manual test plan. It does not send influence probes, reuse credentials or claim a verified vulnerability.
Response headers
Local analysis sends no requests. Maximum input: 128 KiB.
Evidence and limitations
Directive inventory
Response A · baseline
Response B · follow-up
Comparison uses the context checkboxes in Analyze. It does not compare bodies or verify that requests share a cache key.
Reviewable manual PoC
A random query parameter alone does not guarantee isolation. Original query values and fragments are removed from generated requests. No credentials are copied. Review all steps before sending anything.
Test plan & raw requests
No PoC generated. Generated PoC requests are never executed automatically.
How to interpret results
Cache deception
Requires a mismatch in cache/origin interpretation that stores private content and serves it to another client. A static-looking suffix or cache HIT alone does not demonstrate this.
Cache poisoning
Requires attacker-influenced content to be stored under a cache key used by clean requests. Reflection alone does not prove shared persistence or impact.
Policy vs. reality
no-store prohibits storage; no-cache allows storage but normally requires revalidation; private restricts shared caches. Field-qualified directives differ. CDN overrides and multiple cache layers need independent verification.
Evidence collection
Use synthetic account data, separate clients, paired requests, timestamps and body evidence. Record cache attribution and exclude origin-side persistence or authorization failures. Report uncertainty honestly.
Limits
Live GET/HEAD collects response headers only. No automatic scanner, credential-forwarding redirects, body comparison, complete current-age computation, or inference of undocumented CDN cache keys. Exports omit raw headers and URL inputs; review free-form evidence before sharing.