CDN finder
Find the CDN or proxy in front of any website, such as Cloudflare, CloudFront, Fastly, Akamai, Bunny or QUIC.cloud. See the evidence, the edge location that answered, the cache status and which other hosts serve the site's files.
- Evidence shown for every result
- Cache status and edge location
- No signup needed
CDN or proxy
Enter a domain to start
- DomainWaiting for inputWhat you entered
- DNS—CNAME or address
- Edge—Who answered
- Origin—Your server
CDN report
Enter a domain above to see which CDN or proxy serves it, the evidence for it, the edge that answered, the cache status and the hosts that serve its files.
Fair-use limit: 30 checks per hour and 200 per day for each visitor IP address. Results are cached for 10 minutes.
What a CDN does
A content delivery network answers visitors from data centres close to them, in front of your own server.
Edge and origin
Visitors connect to the CDN's edge server. The edge serves a cached copy or fetches the page from your origin server, whose address stays hidden from public DNS.
Caching saves the trip
Images, CSS and JavaScript are usually cached at the edge. HTML is often passed through to the origin unless the CDN or a plugin is set to cache it.
More than speed
Most CDNs also act as a reverse proxy with a firewall, bot protection and DDoS absorption, which is why Cloudflare and others are used even by small sites.
How a site joins a CDN
Either the nameservers move to the CDN, like Cloudflare, or a CNAME points the host to the CDN, like cdn.example.com to a cloudfront.net name.
Signals for common CDNs
The headers and DNS names that identify each provider. The tool checks 15 providers in total.
| Provider | Response headers | DNS and network |
|---|---|---|
| Cloudflare | cf-ray, server: cloudflare |
Cloudflare IP ranges, *.cdn.cloudflare.net |
| Amazon CloudFront | x-amz-cf-id, x-amz-cf-pop |
*.cloudfront.net |
| Fastly | x-served-by: cache-…, x-fastly-request-id |
*.fastly.net, *.fastlylb.net |
| Akamai | server: AkamaiGHost, x-akamai-… |
*.edgekey.net, *.edgesuite.net, *.akamaized.net |
| Bunny CDN | server: BunnyCDN, cdn-pullzone |
*.b-cdn.net |
| QUIC.cloud | x-qc-pop, x-qc-cache |
*.quic.cloud |
| Vercel and Netlify | x-vercel-id, x-nf-request-id |
*.vercel-dns.com, *.netlify.app |
| Azure Front Door | x-azure-ref, x-msedge-ref |
*.azurefd.net, *.azureedge.net |
How this tool works
What happens between pressing Check and seeing the report.
You enter a domain
A link or a bare name works. Use the exact host visitors open, because www and the bare domain can sit behind different services.
DNS is read
Our server follows the CNAME chain and reads the A, AAAA and NS records, plus the reverse DNS name of the first address.
The homepage is requested
One GET request per hop, redirects followed one at a time and every address checked before connecting. Headers and the first 256 KB of HTML are kept.
Signals are scored
Each provider gets points for unique headers, CNAMEs, IP ranges, reverse DNS and nameservers. Two strong signals make a confirmed result.
What this tool does, and what it doesn't
A plain list, so you know exactly what to expect.
This tool does
- Score 15 CDNs and proxies from several signals
- Show the evidence behind each result
- Read the edge location and cache status
- Spot Cloudflare in DNS-only mode
- Name the hosts that serve the site's files
- Show every response header
This tool does not
- Reveal the origin server behind a proxy
- Test speed from many countries
- Know every CDN in the world
- Get past bot protection
- Check private or local addresses
- Keep results longer than 10 minutes
Where your data goes
The domain you enter is looked up in DNS and its homepage is requested by our server, following redirects. The site and its DNS servers see our server's IP address, not yours. Nothing is sent to other services. The result is cached for 10 minutes, then deleted. A hashed, temporary copy of your IP address is used for rate limiting. Like any website, our server may keep normal access logs, as described in our privacy policy.
Why your results might look unexpected
The six surprises people run into most, and what each one means.
Cloudflare nameservers but no CDN
The DNS record is set to DNS only. Visitors go straight to the origin server, so no Cloudflare headers appear.
Two providers found
Multi-layer setups are common: Cloudflare in front of a Vercel or AWS origin, or a WordPress host whose own CDN sits behind Cloudflare.
Edge location in another country
The location is the data centre that answered our server. Your visitors are served from one near them.
Cache shows MISS
The edge had no copy yet, or the cached copy expired. Run the check again: a cacheable page should become a HIT.
403 or a challenge page
Bot protection blocked our server. The CDN is usually still detected from DNS and the headers of the block page.
No CDN, but the site is fast
Good hosting with server-side caching can be fast without a CDN, especially for visitors near the server.
Questions about CDNs
How does the tool know which CDN a site uses?
It combines independent signals: response headers that only one provider sends, such as cf-ray for Cloudflare or x-amz-cf-id for CloudFront, CNAME records that point to a CDN domain, Cloudflare's published IP ranges, reverse DNS names and nameservers. Each signal adds to a score, and the report shows the evidence behind every result.
What does "No CDN detected" mean?
None of the signals matched a provider we know. The site may be served straight from its host, use a CDN that hides its headers and uses its own IP space, or use a provider that is not in our list. Check the response headers block: a Via or X-Cache header often names the system that answered.
Is the edge location where my visitors are served from?
No. The edge location is the CDN data centre that answered our server, which is chosen by where our server is. Your visitors in other countries are usually served by a data centre near them. The code, such as BOM for Mumbai, comes from headers like cf-ray or x-amz-cf-pop.
What do HIT, MISS and DYNAMIC mean?
HIT means the edge served a cached copy without asking your server. MISS means it had to fetch the page from your server first, and the next request may be a HIT. DYNAMIC or BYPASS means the page is not cached at the edge at all, which is the default for HTML on Cloudflare unless you add a cache rule.
Can it find the real server behind Cloudflare?
No. The tool only shows what is publicly visible: the CDN's edge addresses and headers. Hiding the origin server is one of the reasons sites use a CDN, and this tool does not try to get around it. To see where a site without a proxy is hosted, use the hosting checker.
Why do Cloudflare nameservers show, but no Cloudflare CDN?
Cloudflare can run only the DNS for a domain. When the record is set to "DNS only" (grey cloud), visitors connect straight to the origin server and no cf-ray header is sent. Turn on the proxy (orange cloud) to put Cloudflare's CDN and firewall in front of the site.
Is the domain I check stored?
The result is cached on our server for 10 minutes so repeated checks do not hit the site again, then deleted. Our server makes the DNS lookups and the web request, so the site sees our server's IP address, not yours. A hashed, temporary copy of your IP address is used for rate limiting. Like any website, our server may keep normal access logs, as described in our privacy policy.