Network · Made a little simpler

Caching Header Analyzer

Audit saved response headers for private and shared freshness, missing validators, conflicting storage rules and recorded cache outcomes. Compare one or more responses locally.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

Caching Header Analyzer: how to use it

  1. Paste or open a saved text capture. Use one field per line and an HTTP status or a standalone URL to mark each response.
  2. Set a minimum lifetime for review and select Analyze caching headers.
  3. Choose a response to compare lifetimes, recorded cache signals and line-specific findings. Copy or download the full JSON report.

Limits and notes

Up to 120,000 characters and 100 response blocks. Compare recorded fields and optional workflow markers. The lifetime snapshot uses the recorded Age. Date-derived lifetimes use standard GMT HTTP dates. The hit count describes this capture and its recognized signals.

How your privacy works →

Caching Header Analyzer: common questions

Which cache status fields are recognized?

The analyzer reads standard Cache-Status and common CF-Cache-Status and X-Cache values. It shows each observed outcome and uses the nearest recorded member from the first recognized field family in that order for the sample count.

Why can the shared and private estimates differ?

s-maxage applies to shared caches and takes precedence there. max-age supplies the private lifetime. When the relevant directive is absent, the report can use Expires and Date.

Does a short lifetime mean the response policy is wrong?

The threshold highlights responses for review. Check whether the resource is versioned, how often it changes and how quickly clients should see updates.

Guides