Environment Cache Comparator

Trace content from release to visitor

Find where an update becomes outdated.

Compare staging, the production static host, and the public production CDN for every page and discovered static asset.

Staging→Production host→Production CDN

Comparison profile

Sources and release

Comparison name

1 Staging candidate Staging base URL

2 Production CDN Public production URL

3 Production static host Recommended Production hostname / base URL Optional Force connection to public IP Optional

Use the production hostname above and the static-host IP here. The request preserves Host routing and TLS SNI.

Expected release ID Optional

Content updated at Optional

Pages and assets 0 / 20

One path per line. Add || newest text marker when a page has a known update.

Normalize HTMLIgnore origin names, comments, CSP nonces, request IDs, and spacing before hashing. Discover static assetsCompare up to 10 same-origin CSS, JS, image, and font resources from staging pages.

Only public HTTP(S) endpoints on ports 80 and 443 are allowed. TLS verification stays enabled.

Paths checked0

Current / aligned0

CDN stale0

Review / errors0

Evidence

Environment comparison

No comparison has run yet.

⇄Ready to compare

Add the environment URLs and paths, then run the check.

Root-cause guide

How conclusions are made

All aligned: staging, production host, and CDN match.

CDN stale: production host has the new release, but CDN does not.

Not deployed: staging is new, but the production host is still old.

Production differs: host and CDN agree but intentionally or unexpectedly differ from staging.

Release IDs and expected markers are strongest. Static-file hashes are strong. Normalized HTML and cache headers are supporting evidence.