Cache-Control Checker

Cache-Control Checker

Analyze browser and shared cache policy, TTL and revalidation signals.

Enter a website URL to start

Website caching and origin control

What is Cache-Control?

Cache-Control tells browsers, proxies and CDNs whether a response may be stored, for how long and when it must be revalidated.

Policies should match the content. Fingerprinted static assets suit long immutable caching, while dynamic HTML must account for publishing, authentication and personalization.

What is checked

TTL

Browser and shared TTL

Separate max-age, s-maxage, private, public and no-store behavior.

VALID

Revalidation signals

Review ETag, Last-Modified, no-cache and conditional-request foundations.

VARY

Cache-key risks

Find Vary: * and missing shared-cache lifetime.

Why check cache configuration?

Missing TTLs cause repeated origin requests; excessive TTLs serve stale content; no-store and Vary: * can prevent edge reuse.

Reduce origin traffic

Let reusable responses come directly from browsers and edge nodes.

Prevent stale content

Find unsuitable TTLs and confirm validators are available.

Separate browser and CDN

Explain private, public, max-age and s-maxage independently.

How does the Cache-Control checker work?

The tool requests one public page and analyzes the final response headers. Results use short caching and are not stored as history.

  1. 01

    Request the page safely

    Normalize the URL and bound redirects, addresses, time and response size.

  2. 02

    Parse cache directives

    Read Cache-Control, Expires, Age and directive values.

  3. 03

    Classify cache scope

    Determine whether browser and shared caches may store the response.

  4. 04

    Recommend changes

    Explain missing, disabled, TTL and Vary problems.

Cache-Control checker FAQ

How do max-age and s-maxage differ?

max-age applies to browser and shared caches; s-maxage overrides the shared-cache TTL.

Does no-cache disable caching?

No. It permits storage but requires revalidation before reuse. no-store forbids storage.

Should HTML be cached for one year?

Usually not. Long immutable caching is better for content-hashed static assets.

Are results stored?

No business database record is created; only short caching reduces duplicate requests.