Cache-Control Header Analyzer
Read saved Cache-Control and Age fields. Compare the declared freshness lifetimes, revalidation requirements and storage restrictions in a local report.
Compare Private and Shared Cache Freshness
Paste a raw value, named field lines, or a saved response with its HTTP status line. For captures, the report uses the last non-informational block when one exists.
Cache-Control Header Analyzer: how to use it
- Paste a Cache-Control value, named fields or saved response headers. You can also load the example.
- Use the captured Age field or supply a known Age in seconds. Analyze Cache-Control.
- Compare private and shared caches. Check warnings about repeated values and download the JSON report if needed.
Limits and notes
Up to 50,000 input characters and 300 directives. The report uses the last non-informational capture block, when available. Explicit lifetimes and recorded Age describe a snapshot. The analyzer does not compute freshness from dates, request headers or heuristic rules.
How your privacy works →Cache-Control Header Analyzer: common questions
When does s-maxage replace max-age?
For a shared cache, s-maxage supplies the explicit freshness lifetime when present. A private cache uses max-age.
Can a cached response be fresh and require validation?
Yes. An unqualified no-cache directive requires validation before reuse even within the freshness lifetime.
What if my response contains two max-age values?
The report marks the applicable lifetime as unavailable. RFC 9111 permits recipients to use the first value or treat the response as stale.