CDN Cache Checker: HIT or MISS Worldwide
Request a URL from up to 12 locations and see which CDN answers, whether each edge served it from cache (HIT or MISS), the cache age and the edge location.
How it works
Reading cache headers
HIT and MISS
A HIT means the edge answered from its own cache without asking your origin; a MISS means it had to fetch the page first. A healthy cached site shows mostly HITs after the first run.
Age
The Age header says how many seconds the copy has been in the cache. A missing or zero Age on every request usually means the page is not cacheable.
Why pages are not cached
Set-Cookie, Cache-Control: private or no-store, and query strings that change on every request are the usual reasons a CDN passes requests straight to the origin.
FAQ
Frequently asked questions
Which CDNs are recognised?
Yeap CDN, Cloudflare, Amazon CloudFront, Fastly, Akamai, Vercel, Netlify, bunny.net, Google and Alibaba Cloud CDN are detected from their response headers.
Why do some locations show MISS every time?
Each edge keeps its own cache. Edges that get little traffic for your site evict it sooner, and tiered caching may answer from a parent cache instead.
Does the check purge or warm my cache?
It sends one normal GET request per location, which may fill the cache at those edges, but it never purges anything.
More free tools
All toolsGlobal acceleration with HTTP/3