Skip to main content

How to fix: Age header reveals CDN cache age

The Age header is present and reveals how long the response has been cached at a CDN or proxy.

Why it matters

Age headers reveal CDN infrastructure is in use and indicate whether a response is served from cache, helping attackers time cache-poisoning attacks or infer when cached entries will expire.

Age is a standard HTTP header; consider removing it for sensitive responses if it reveals operational details.

How to fix it

  1. 1For sensitive responses, set Cache-Control: no-store (CDN will not cache them, so Age will not appear)
  2. 2For public resources, Age is expected behavior and low risk

Code examples

Remove Age for sensitive endpoints

nginx
location /api/ {
  proxy_hide_header Age;
  add_header Cache-Control "no-store, max-age=0";
}

References

Detected automatically by VulnRadar. The check id is age-header-reveals-cdn, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Age header reveals CDN cache age?
VulnRadar rates this info severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id age-header-reveals-cdn, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for age header reveals cdn cache age

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Age header reveals CDN cache age | VulnRadar