Website CDN Checker
Find out which content delivery network serves a site. The checker looks at three kinds of evidence: CDN-specific response headers such as cf-ray, x-amz-cf-id or x-served-by, the CNAME chain of the host name, and the network that owns the server’s IP address. It recognises Cloudflare, Amazon CloudFront, Fastly, Akamai, Azure, Google Cloud, Vercel, Netlify, Bunny, Sucuri, GitHub Pages and QUIC.cloud, for the page and for the hosts of its assets, with their cache status.
- Encrypted connection
- No sign-up
- Free to use
How to use Website CDN Checker
- Enter the page address.
- Click “Detect CDN”.
- Read the CDN and the evidence.
- Check the asset hosts.
Website CDN Checker features
Three signals
Headers, CNAME, IP owner.
12 CDNs
Major providers.
Asset hosts
Each checked separately.
Cache status
HIT or MISS.
Safe fetching
Public addresses only, with size and time limits.
Evidence shown
Why a CDN was detected.
When to use Website CDN Checker
- Competitor and technology research.
- Checking that a CDN is active.
- Debugging caching.
- Security reviews.
Website CDN Checker FAQ
Can every CDN be detected?
No. Some hide their identity; then no CDN is reported even if one is used.
Why do assets use a different CDN?
Images and scripts are often served from a separate CDN or a third-party host.
What is an ASN?
The number of the network that owns an IP address, such as AS13335 for Cloudflare.
Does a CDN make a site faster?
Usually, especially for visitors far from the origin server.
Can a site use more than one CDN?
Yes. Some sites use one CDN for the page and another for images or video, or switch between CDNs by region.
Does a CDN make every site faster?
Usually, for visitors far from your server and for static files. The benefit is smaller for small local sites with nearby visitors.
Can I see whether a page came from the CDN cache?
Headers such as cf-cache-status or x-cache show HIT when the CDN served its cached copy and MISS when it fetched the file from your server.
Who delivers a website
A CDN serves copies of a site from servers close to visitors and often adds protection and compression. Knowing which one is used helps with debugging and comparisons.
Use the Cache Checker to see what the CDN actually caches.
A content delivery network serves a site from servers close to each visitor. The checker looks at three kinds of evidence: CDN-specific headers such as cf-ray, x-amz-cf-id or x-served-by, the CNAME chain of the host name, and the network that owns the server’s IP address.
Combining the signals is more reliable than any single one: a site can use a CDN for assets only, or put a security proxy in front without caching. The result names the CDN when it is recognised and shows the evidence, so you can judge it yourself.
Knowing the CDN helps when debugging caching headers, comparing performance with competitors or checking that a migration to a new CDN went live everywhere.
Typical uses are confirming that a CDN migration reached every domain and subdomain, checking which network a competitor uses, and debugging caching problems where it is unclear whether a response came from the CDN or the origin server. The evidence list makes it possible to verify the result yourself.
Some security services such as web application firewalls also add CDN-like headers, so a recognised network does not always mean the files are cached at the edge.