Cloudflare Cache Checker

Check the real Cloudflare cache status of any URL. Our server fetches the URL and reads all response headers directly — no guessing, no simulation.

cf-cache-status

N/A

cf-ray

N/A

cf-ipcountry

N/A

Cache Age

N/A

cache-control

N/A

All Response Headers

Header	Value

Cloudflare Cache Status Values Explained

The cf-cache-status header tells you exactly what Cloudflare did with the request. Here is what each value means and what action to take.

HIT

Served from Cloudflare edge cache

→ Good — no origin request made

MISS

Not cached — fetched from origin

→ Review cache-control headers

BYPASS

Cache deliberately bypassed

→ Check Page Rules / cookies

EXPIRED

Cached but TTL expired, re-fetched

→ Increase max-age TTL

DYNAMIC

Dynamic content, not cacheable

→ Normal for authenticated pages

REVALIDATED

Validated with origin, still fresh

→ Content unchanged, cache OK

STALE

Stale copy served while updating

→ Configure stale-while-revalidate

UPDATING

Cache entry being refreshed

→ Transient — check again shortly

When to Use This Tool

Caching problems are invisible — you only notice them when your site is slow or your users get stale content. This tool makes the invisible visible.

Verify caching rules work

After setting Cloudflare Page Rules or Cache Rules, confirm your URLs are returning HIT instead of MISS.

Debug cache BYPASS issues

Find out why Cloudflare is not caching a page — cookies, headers, or bypass rules are the usual suspects.

Check cache after purge

After purging Cloudflare cache, confirm the first request gets a MISS and subsequent requests return HIT.

Non-Cloudflare CDN headers

The tool shows X-Cache, Via, and other CDN headers too — useful for debugging Fastly, Varnish, or AWS CloudFront.

Performance troubleshooting

A MISS on every request means every user hits your origin. Fixing cache saves bandwidth and cuts page load times drastically.

Audit new deployments

After a site deployment, check that static assets (JS, CSS, images) are returning HIT from Cloudflare's edge.

Key Features

Check real cf-cache-status header: HIT, MISS, BYPASS, EXPIRED, DYNAMIC

View CF-Ray ID, cf-ipcountry, and cache age in seconds

See full response headers table with Cloudflare headers highlighted

Detect whether a URL is behind Cloudflare at all

Check cache-control, etag, last-modified, and expires headers

Server-side check — no browser cache interference

Frequently Asked Questions

What is cf-cache-status?

cf-cache-status is a response header added by Cloudflare to every response. It tells you whether the response was served from Cloudflare's edge cache (HIT), fetched fresh from your origin server (MISS), deliberately bypassed (BYPASS), or was dynamic content not eligible for caching (DYNAMIC).

What does a cache MISS mean and how do I fix it?

A MISS means Cloudflare did not have a cached copy and had to fetch the page from your origin server. Common causes: Cache-Control: no-store/no-cache headers, cookies triggering bypass, or the content type not being cacheable. Fix: Set appropriate cache-control headers, use Cloudflare Page Rules or Cache Rules to cache more aggressively.

Why does Cloudflare show BYPASS for my page?

BYPASS is triggered when a request matches a Cloudflare bypass rule, when cookies (like WordPress login cookies) are present, or when the origin returns Cache-Control: no-cache. Check your Page Rules / Cache Rules and remove unnecessary cookies from Cloudflare bypass conditions.

What is a CF-Ray ID?

CF-Ray is a unique identifier for every request that passes through Cloudflare. It encodes the data centre (PoP) that handled the request and a unique request ID. If you contact Cloudflare support, they use this ID to look up the exact request in their logs.

How is this different from checking cache in my browser?

Your browser cache stores files locally and may show a cached response even if Cloudflare itself is not caching. Our tool checks from our server with a fresh HTTP request — no local cache, no cookies, no browser extensions — giving you the real Cloudflare-side cache status.

Does this work for non-Cloudflare sites?

Yes. If the URL is not behind Cloudflare, the tool still shows all response headers (Cache-Control, X-Cache, Expires, ETag etc.) and flags that no Cloudflare headers were detected. This helps debug caching on any CDN.

What is cache age and why does it matter?

Cache age (the Age header) tells you how many seconds ago the cached copy was stored at the edge. A high age means the content has been cached for a long time. If your content changes frequently, a very high age may mean stale content is being served.

Is the Cloudflare cache checker free?

Completely free. No Cloudflare account needed, no API key, no sign-up. Enter any URL and see the real cache status instantly.

Related Tools

Redirect Checker

Analyze URL redirects and trace redirect chains.

SEO Checker

Analyze your website for SEO issues and improvements.

Website Speed Test

Test your website loading speed and performance.

Sitemap Generator

Crawl any website and generate professional XML sitemaps.

XML Sitemap Validator

Validate your XML sitemap for errors.

What is My IP

Find your public IP address and location details.