Find out which CDN sits in front of a site
Enter a URL and the Network Inspector reads the edge fingerprints — cache-status headers, server signatures, ASN and the network path — to identify the CDN delivering it.
Runs in the Network Inspector — no account, nothing to install.
Sample report · illustrative data
Everything the report surfaces
Edge fingerprinting
Reads the tell-tale headers CDNs add — CF-Ray, X-Cache, X-Served-By, Via and Server — to name the provider behind a site.
Cache hit or miss
Surfaces the cache-status header so you can see whether the edge is serving content from cache or falling through to origin.
Network path & ASN
Resolves the serving IP and its autonomous system, confirming the network the request actually terminates on.
Multi-CDN awareness
Distinguishes an origin behind one CDN from stacked layers, so you understand the full delivery chain, not just the first hop.
Three steps to a full answer
Enter a URL
Point the detector at any public site or asset host.
We read the edge
The Network Inspector requests the resource and inspects its headers, IP and ASN for CDN signatures.
See the provider
Get the identified CDN, whether the response was cached, and the network path the request took to reach you.
Find out which CDN sits in front of a site
Open the Network Inspector and get your answer in seconds.
Go deeper in the reference library
Common questions
How can I tell which CDN a website uses?
CDNs leave fingerprints in the response — headers such as CF-Ray, X-Cache and Via, distinctive Server values, and the ASN of the serving IP. The detector reads all of these and names the provider.
Can it tell if a response was served from cache?
Yes. Most CDNs report a cache-status header (for example X-Cache: HIT or a cf-cache-status value). The detector surfaces it so you can see whether the edge served cached content or fetched from origin.
What if a site is behind more than one CDN?
The detector looks at the whole delivery chain, so it can distinguish a single edge from stacked providers and show the network the request ultimately terminated on.
Why does knowing the CDN matter?
The CDN shapes caching, TLS termination, security filtering and performance. Knowing which one is in front of a site tells you where to tune cache rules and where issues are likely to originate.