Check the evidence behind a CDN.
Example
Evidence
Behind the CDN
Response headers
Findings
Capabilities and processing
Enter a domain or paste response headers (from curl -I or DevTools). For a domain, our server reads the CNAME chain, looks up the network of each address and fetches the public HTTPS site with up to three redirects; pasted headers are read in your browser.
The three signals are shown side by side, each with what it points to. Cache status and origin hints, such as an S3 request ID passed through the CDN, come from the same response.
Example workflow
The sample name is behind a CDN on all three signals, and one response header still names the storage service behind it.
Limits and interpretation
A single signal can mislead: a proxy can strip its headers and a CNAME can be left over. The verdict uses headers from the original host. Redirects are followed with public-address checks; Heal it lets you inspect the final host separately. Nothing is stored.