HIT
The response reports a resource found in Cloudflare’s cache. It describes this request, not your whole website.
TWO REQUESTS. A CLEARER PICTURE.
Is your URL returning a Cloudflare cache hit?
Inspect two requests from a single Cloudflare location.
Caching rules can get complicated. Use this tool to check whether the pages and files you intended to cache return the expected Cloudflare cache status. It makes two requests from one location and shows the response headers, helping you spot unexpected cache misses or bypasses.
OBSERVED RESPONSE
These are server-side Worker requests. Browser results may differ. Missing headers do not prove a site is not using Cloudflare. No target response body is displayed or stored by the app.
READ THE SIGNALS
The response reports a resource found in Cloudflare’s cache. It describes this request, not your whole website.
The response reports a cache miss. A second request may hit, but cache fills, rules, and routing can affect the result.
The resource was not eligible for caching, or caching was bypassed. Dynamic pages can legitimately return these statuses.
No. It checks only the submitted URL and follows its redirects. Cached images and scripts say nothing about whether the page’s HTML is cached.
One Cloudflare Worker handles each check. The report shows its incoming Cloudflare location code when available. This is not an independent regional probe, and outbound routing or tiered caching can involve other locations. A response’s CF-Ray suffix is shown as reported, not a guarantee of the cache-serving location.
Cookies, authentication, request headers, bot protection and network routing can change the result. Our requests use a fixed diagnostic user agent, no browser cookies, no cache-busting query parameters and no cache overrides.
No. It shows the headers returned for these requests. Headers can be changed by servers or Workers. It does not inspect your Cloudflare configuration, calculate a cache hit ratio, or certify a site’s setup.
Up to 10 checks per minute per IP in the local Cloudflare rate-limit scope. Each attempt has a 12-second timeout and a 2 MB body-read limit. Reaching the limit can prevent a full cache fill; the report flags that condition.