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.
CDNs in short
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.
How it works: our server downloads the page once through a guarded fetcher that only connects to public addresses, follows a limited number of redirects and stops after a size and time limit. The HTML is then analysed in your browser as inert text – scripts on the page never run and nothing is stored.
What it cannot see: content and resources that a page adds with JavaScript after it loads, pages behind a login, and servers that block automated requests. For those, open the page in your browser, use its developer tools, or paste the page source where the tool offers a paste option.
Use the results as a starting point: fix the items marked red first, review the yellow warnings in context, and run the check again after a change. Requests are rate-limited to keep the service fair; if you check many pages in a row, wait a few minutes.
Related checks on this site cover the rest of a technical review – speed and Core Web Vitals, security headers, structured data, accessibility and SEO signals – so you can work through a whole site audit one topic at a time.
Who it is for: site owners checking their own pages, developers debugging a release, SEO and marketing teams auditing clients or competitors, and students learning how the web works. No account or installation is needed, and the results are plain text and tables you can copy into a report or ticket.