Cache Verifier

Compare what visitors receive

Is your CDN serving the newest content?

Check pages and discovered assets from the server, inspect cache headers, and compare a normal response with a cache-bypassed probe. Add an expected text marker for the strongest freshness result.

How it works

Request the public URL normally.
Request it again with a unique query and no-cache headers.
Compare content hashes, markers, cache state, age, and TTL.

Configuration

Targets

Base website URL Optional for full URLs

Required only when you enter paths such as /pricing.

Page paths or full URLs 0 / 20

One target per line. Optionally add || expected newest text to verify a deployment marker.

Expected CDN / edge identifier Optional

Matched against Via, Server, X-Cache, CF-Ray, and X-Served-By.

Discover page assets Also inspect up to 10 CSS, JavaScript, font, and image URLs found in the HTML.

Only public HTTP(S) targets are allowed. Private and local network addresses are blocked.

Checked0

Current / consistent0

Needs review0

Errors0

Results

Response comparison

No verification has run yet.

Ready to inspect

Enter one or more public pages, then run the verification.

Interpretation

A cache HIT does not mean stale

Current: expected newest text exists in the normal response.

Stale: expected text exists only in the bypassed response.

Review: hashes differ, the marker is absent, or headers cannot prove freshness.

Consistent: both probes have the same hash, but no marker was supplied.