Browser and CDN cache audit

Cache-Control Header Checker

Understand whether a URL can be cached, for how long and why a CDN may report a hit, miss or bypass.

Tests one live public response; results can change when the site configuration changes.

✓ Free to use ✓ No account required ✓ Up to 20 redirect hops
1

Inspect HTTP caching behavior

The audit parses Cache-Control and reports Age, CDN cache status, validators, expiry, Vary and other cache-related headers.

2

Interpret the result

Set deliberate browser and shared-cache lifetimes, retain validators where useful and investigate unexpected bypass or no-store responses.

3

Prioritize fixes

One request cannot prove every cache node is configured identically or predict a later hit after cache warming.

How to interpret HTTP caching behavior

The audit parses Cache-Control and reports Age, CDN cache status, validators, expiry, Vary and other cache-related headers. One request cannot prove every cache node is configured identically or predict a later hit after cache warming.

What the tool evaluates

The audit parses Cache-Control and reports Age, CDN cache status, validators, expiry, Vary and other cache-related headers.

  • The audit parses Cache-Control and reports Age, CDN cache status, validators, expiry, Vary and other cache-related headers.
  • Set deliberate browser and shared-cache lifetimes, retain validators where useful and investigate unexpected bypass or no-store responses.
  • One request cannot prove every cache node is configured identically or predict a later hit after cache warming.

Problems and next steps

Set deliberate browser and shared-cache lifetimes, retain validators where useful and investigate unexpected bypass or no-store responses.

Frequently asked questions

What does this tool check?

The audit parses Cache-Control and reports Age, CDN cache status, validators, expiry, Vary and other cache-related headers.

How should I use the result?

Set deliberate browser and shared-cache lifetimes, retain validators where useful and investigate unexpected bypass or no-store responses.

What are the limits?

One request cannot prove every cache node is configured identically or predict a later hit after cache warming.

Related URL tools and guides