Detect Any Site's CDN Provider
Instantly check if a website uses a Content Delivery Network and identify the provider — Cloudflare, CloudFront, Fastly, Akamai and 8+ others — with step-by-step detection status.
What is a Content Delivery Network?
A globally distributed network of servers designed to serve cached web assets and optimize content delivery pipelines.
Distributed Edge Servers
A CDN can cache and serve web content from distributed edge locations, reducing the physical distance between users and the infrastructure hosting the origin content.
Speed & Performance
By routing user requests to optimized server locations, latency is reduced. Users are typically served from an edge location selected to provide efficient network performance.
Security & DDoS Protection
CDNs act as proxy layers, buffering server infrastructure from direct incoming traffic spikes, neutralizing common DDoS attacks, and offering customizable Web Application Firewalls (WAF).
How Detection Works
We detect CDNs through multiple independent signals: HTTP response headers, DNS record configurations, and edge IP range mappings managed by major service providers.
CDN Finder
Enter just the domain (e.g. netflix.com) or the full URL. We'll strip the protocol automatically.
Privacy note: the domain is resolved and checked entirely from our backend server without sending your queries to third-party tracking APIs. Your query is not stored after the request completes.
12 Major CDN Providers We Detect
Each CDN has unique fingerprints we look for in headers, DNS, and IP ranges.
| Provider | Signature Headers | DNS / CNAME Pattern | Best For | Pricing |
|---|---|---|---|---|
☁️Cloudflare |
cf-ray, server: cloudflare, cf-cache-status |
No standard CNAME (uses NS delegation), but IP ranges are published | A widely used CDN and security platform. Includes free tier protection. | Free tier |
AWSCloudFront |
x-amz-cf-id, x-amz-cf-pop, via: CloudFront |
*.cloudfront.net |
AWS-native CDN. Tight integration with S3, Lambda@Edge. | Pay-as-go |
⚡Fastly |
x-served-by, x-fastly-request-id, server: Fastly |
*.fastly.net |
Edge computing (VCL/WASM). Used by GitHub, Reddit, Shopify. | Enterprise |
🌐Akamai |
x-akamai-transformed, x-cache: TCP_HIT from Akamai |
*.akamaiedge.net, *.akamai.net |
Enterprise media/streaming. Largest edge network globally. | Enterprise |
GGoogle Cloud CDN |
via: google, server: Google Frontend |
No standard CNAME (uses Anycast IPs via Google Cloud Load Balancing) | GCP-native. Integrates with Cloud Load Balancing. | Pay-as-go |
▲Vercel |
x-vercel-id, server: Vercel, x-vercel-cache |
*.vercel.app, cname.vercel-dns.com |
Frontend deployments (Next.js). Edge functions built-in. | Free tier |
NNetlify |
x-nf-request-id, server: Netlify |
*.netlify.app |
Static sites + Jamstack. Built on AWS infrastructure. | Free tier |
🛡️Sucuri |
x-sucuri-id, server: sucuri, x-sucuri-cache |
*.sucuri.net |
Security-first CDN. WAF + malware scanning + DDoS. | Security |
🐰BunnyCDN |
server: BunnyCDN, x-bunny-cf-storage |
*.b-cdn.net |
Affordable global CDN. Popular with indie devs and small sites. | Pay-as-go |
📘Azure CDN / Front Door |
x-msedge-ref, server: ecacc |
*.azureedge.net, *.vo.msecnd.net |
Microsoft Azure-native CDN profiles and application routing. | Pay-as-go |
🔑KeyCDN |
server: keycdn-engine, x-edge-location |
*.kxcdn.com |
High-performance content delivery, budget-friendly enterprise. | Pay-as-go |
🛡️Imperva (Incapsula) |
x-iinfo, x-cdn: imperva |
*.incapsula.net |
Enterprise WAF + DDoS + CDN. Security-focused. | Security |
How to Use This CDN Finder
Four steps from domain to full detection report.
Enter domain
Type or paste any domain — netflix.com, github.com, etc.
Click Detect
Watch live status as we resolve DNS, fetch headers, and match IP ranges.
Review results
See CDN provider, edge IP, and all matching evidence.
Act on findings
Use insights for competitor research, debugging, or infrastructure decisions.
How We Detect CDNs — Multiple Independent Signals
Cross-validating multiple public server outputs provides verifiable results even when some signals are restricted.
1. HTTP Response Headers
Many CDN configurations expose recognizable fingerprints in response headers. Cloudflare sends cf-ray, CloudFront sends x-amz-cf-id, and Fastly sends x-served-by.
2. DNS CNAME Records
Most CDNs are configured via DNS delegations. A CNAME pointing to *.cloudfront.net is an explicit indicator of AWS CloudFront. We query DNS for public CNAME patterns.
3. IP Address Ownership
CDNs publish public IP range definitions. If the resolved target IP falls within Cloudflare's known CIDR blocks (like 104.16.0.0/13), we identify a Cloudflare IP-range match.
4. Cross-Signal Validation
By cross-referencing matched headers, DNS records, and IP ranges, we consolidate findings to identify the provider even when individual indicators are restricted.
Honest by Design — What This Tool Does and Doesn't Do
This tool analyzes publicly available DNS and HTTP data. Here is exactly what it does and does not do:
- ✓ Uses multiple independent signals (headers + DNS + IP ranges) for validation.
- ✓ Shows matched evidence transparently — including headers, CNAMEs, and IP range blocks.
- ✓ Detects 12 major CDN providers including Cloudflare, CloudFront, Fastly, Akamai, Vercel, Netlify.
- ✓ Does not guarantee detection — some custom and enterprise networks hide standard indicators.
- ✓ Does not bypass Cloudflare's proxy to reveal the origin IP — that is outside the scope of this utility.
- ✓ Does not store the domains you check.
This tool does
- Detect 12 major CDN providers
- Cross-validate via headers, DNS, and IP ranges
- Show matched evidence transparently
- Reveal the public edge server IP address
- Operate entirely from a first-party, private backend
- Handle domains with or without https://
This tool does not
- Reveal origin IP behind proxy networks
- Detect custom/private internal CDNs
- Guarantee detection of highly customized networks
- Store the domains you check
- Scan for vulnerabilities
- Require third-party API dependencies
When to Use This CDN Finder
Use the tool for these common scenarios.
Common Results and What They Mean
Understanding the different detection outcomes.
CDN Detected
One or more CDN providers identified with clear evidence.
What to do: Review the evidence. For infrastructure analysis, evaluate the detected provider's features for your own stack.
No CDN Detected
The tool did not find enough public evidence to identify a supported CDN.
Causes: The site does not use a CDN, uses a CDN not in our database, or has stripped identifying signatures.
Multiple CDNs Detected
Two or more CDN providers matched — indicating a multi-CDN setup.
Example: A site might use Cloudflare for DNS/WAF protection in front of an AWS CloudFront asset storage distribution.
Could Not Resolve
DNS lookup failed for the domain.
Causes: Domain doesn't exist, has no active DNS records, or local servers are unreachable. Check domain spelling.
Hidden CDN
Site uses a CDN but has stripped identifying headers.
Fix: Some enterprise setups run stealth. IP range checks usually still work since public IP registration blocks remain allocated to providers.
Edge IP ≠ Origin IP
The IP shown is the CDN's edge server, not the real origin.
Why: That is standard proxy behavior. Real-world target servers remain isolated for security and performance.
Related CDN, Performance & Infrastructure Tools
CDN Finder FAQs
Answers based strictly on what this tool does and how CDNs work.
How accurate is the detection?
Detection is based on multiple public signals such as HTTP headers, DNS records, and IP ranges. Results are generally useful for major CDN configurations, but detection is not guaranteed, especially when providers or site owners hide or customize identifying signals.
What does "No CDN Detected" mean?
The tool did not find enough public evidence to identify a supported CDN. This can mean the site does not use a CDN, uses a CDN that is not in our detection database, or actively hides its CDN signals.
Why does the tool show the CDN's IP, not the origin IP?
When a site uses a CDN, its DNS records point to the CDN's edge servers. The edge IP shown is the CDN's node, not the real origin server. This configuration is standard to shield origins from performance bottlenecking and secure them from direct attacks.
Can this tool reveal the real origin IP behind Cloudflare?
No. This is a detection tool, not an origin-bypass utility. Revealing origin IPs behind network proxies requires customized penetration-testing practices and is omitted from this public service.
Can a CDN be hidden from detection?
Yes. Custom enterprise configurations can strip identifying headers and use generic DNS routing. However, IP range checks usually still work since IP address blocks assigned to major providers are publicly registered.
Why are there usage limits?
To ensure fair access: 30 checks/hour per IP and 200/24 hours per IP. Each check executes server-side DNS queries and an HTTP validation to the target host, consuming local resources.
Are the domains I check stored?
No. The domain is resolved and checked entirely from our backend server without sending your queries to third-party tracking APIs. The data is not stored after the request completes.
Can I detect multiple CDNs on one site?
Yes. Multi-CDN setups (e.g., Cloudflare + CloudFront) are common. If we find signatures from multiple providers, all are reported. The "evidence" section shows which signals matched which provider.