CNAME chain
Resolve the final hostname and match known edge-domain evidence.
Identify CDN providers from CNAME and response-header evidence without unsupported guesses.
Enter a website URL to start
Edge networks and proxy caching
A CDN proxies and caches content across distributed edge nodes to reduce network distance and can add security, compression and protocol features.
CDNs can hide origins and remove identifying headers. An unconfirmed result does not prove that no CDN exists; it means public evidence was insufficient.
Resolve the final hostname and match known edge-domain evidence.
Check high-confidence signals such as CF-Ray, X-Amz-Cf and X-Vercel-Id.
Show Via, Age and X-Cache without guessing a provider from them alone.
Knowing the real delivery layer helps diagnose cache misses, exposed origins, routing differences and conflicting proxy policies.
Check whether DNS and headers point to the expected edge service.
See Age, X-Cache and provider cache-state evidence.
Do not force a provider conclusion without strong evidence.
The tool reads public DNS and one page response. It does not call an external identification API or store history.
Follow safe redirects and identify the final public URL and IP.
Resolve up to five CNAME levels for known edge domains.
Use provider-specific headers and Server markers.
Separate confirmed providers, generic proxy evidence and unconfirmed results.
CNAME flattening, custom hostnames, hidden headers and layered proxies can remove provider fingerprints.
No. It is generic and must be combined with provider-specific headers or CNAME evidence.
No. Coverage, cache hit ratio, origin distance, protocols and configuration all matter.
No origin enumeration is performed; only current public resolution and the final connection IP are shown.
After confirming the CDN, check caching, compression and modern protocols.