CDN Checker — is a site behind a CDN?
Detect whether a website is served through a CDN or WAF such as Cloudflare, Fastly, Akamai, BunnyCDN, KeyCDN or Vercel.
How to read the result
- CDN / WAF
- The content delivery network or firewall identified in front of the site, matched against the fingerprints its edge leaves in the response headers — Cloudflare's
cf-ray, CloudFront'sx-amz-cf-id, and so on. - Server
- The server software named in the response. With a CDN in the path this is usually the CDN's own name rather than the origin's.
- No CDN detected
- No known signature matched. That is not proof there is nothing in front — only that nothing announced itself.
- Proxied or DNS-only
- Cloudflare in particular can be set up two ways: proxying traffic through its edge, or just answering DNS while traffic goes straight to the origin. Only the first shows up here, and only the first gives you caching, the firewall or origin hiding.
Where this tool is wrong
Every check here reads one signal, and each has a blind spot worth knowing before you act on the answer.
- Detection is signature-based. A CDN configured to strip its identifying headers is invisible here, and some enterprise deployments do exactly that.
- Finding a CDN does not mean caching is switched on. Cloudflare in particular is often used purely for DNS and certificates with proxying disabled, in which case it sits in the answer but not in the traffic.
- We read one response to the homepage. A site can route some paths through a CDN and serve others straight from the origin.
Common questions
Cloudflare is detected but my site is still slow. Why?
A CDN only speeds up what it is allowed to cache. If caching rules are not configured, or the pages are dynamic and marked uncacheable, every request still travels to the origin and the CDN adds a hop rather than removing one.
Can a site use a CDN without this detecting it?
Yes. Detection relies on the edge identifying itself in a header, and that can be turned off. A negative result here is weak evidence; a positive one is strong.
Is a CDN worth it for a small site?
For a site whose visitors are all in one country and whose host is in that country, the speed gain is small. The certificate handling, the absorption of traffic spikes and the firewall are usually the better reasons.
Does a CDN hide my server's real IP address?
It hides it from casual lookups, which is most of them. It does not hide it from someone who checks historical DNS records, mail headers or a certificate transparency log — origin hiding works only if the origin also refuses connections that do not come through the CDN.