Cache is invisible until it makes you look broken. Seven layers could be holding the old copy, each with a different fix — and clearing the wrong one just wastes an afternoon. Paste a URL and find out which.
We fetch your page as a visitor gets it, then again with caching defeated, and compare.
Public web addresses only. We read response headers and compare two fetches — nothing is stored, and we never log the URLs you check.
Most stale-cache problems are one missing header. Pick your server and what you want.
Listed closest-to-reader first, which is also cheapest-to-test first.
The checker tells you which layer is holding the old copy. These eight tell you which button clears it, taken from each vendor’s own documentation and linked so you can check.
The server page cache on LiteSpeed hosts, Hostinger included. Read the header, purge it, and stop it coming back.
Read the guide → CDN EDGEWhat every cf-cache-status value means, purging one URL or everything, and the browser TTL that outlives a purge.
Two caches with two clear buttons. Which one is serving you, and the order to clear them in.
Read the guide → WORDPRESSSpot which plugin built the page from its fingerprint in the HTML, and where each one keeps its clear button.
Read the guide → PLATFORMEvery x-vercel-cache value, why a redeploy is not a purge, and which Cache-Control header actually wins.
Reading Cache-Status, why a short max-age on assets is ignored, and purging by cache tag.
Expose $upstream_cache_status, then fix the two settings that keep nginx serving the old copy.
The layer no purge reaches. How to unregister it, empty the Cache API, and why your new worker never installs.
Read the guide →