Cloudflare Checker
- Non-Intrusive Scan
- DNS and HTTP headers
How do you check if a website uses Cloudflare?
Three public signals show it. Cloudflare answers DNS queries for proxied records with addresses from its published IP ranges, its responses carry a CF-Ray header and usually Server: cloudflare, and zones on Cloudflare DNS usually use nameservers ending in ns.cloudflare.com. The checker reads all three, so it can tell proxied traffic apart from a domain that only uses Cloudflare for DNS.
As a WAF detector it answers one question: does traffic pass through Cloudflare's edge, where its WAF and DDoS protection run? Which rules are switched on cannot be seen from outside. The Cloudflare Checkup reviews that with read-only access to your own account.
What the Cloudflare checker looks at
IP addresses
The hostname's A and AAAA records, compared with Cloudflare's published IPv4 and IPv6 ranges. Proxied records return Cloudflare anycast addresses instead of the origin server's.
CF-Ray and Server headers
One HTTPS request to the hostname. Cloudflare adds CF-Ray to proxied responses, which normally also carry Server: cloudflare. A cf-mitigated: challenge header means Cloudflare served a challenge page.
Nameservers
The zone's NS records. Standard Cloudflare nameservers end in ns.cloudflare.com, and Foundation DNS uses foundationdns.com, .net and .org. Custom nameservers on the customer's own domain cannot be recognised.
Partial (CNAME) setup
A CNAME to a name ending in cdn.cloudflare.net means Cloudflare proxies the hostname while DNS stays with another provider, a setup Cloudflare offers on Business and Enterprise plans.
What the result means
Proxied through Cloudflare
Traffic for the hostname goes through Cloudflare's network, where WAF rules, DDoS protection and caching can apply. The account behind it is not visible from outside: it may be the site owner's or a hosting provider's.
Cloudflare DNS only
The zone uses Cloudflare nameservers, but the hostname resolves straight to the origin server, so Cloudflare's proxy features do not apply to it and the origin's IP address is public.
Not on Cloudflare
None of the signals point to Cloudflare. The site may use another CDN or WAF, or none.
Related checks and next steps
- Cloudflare Checkup
Review your own account's WAF, SSL/TLS, DNSSEC and security settings with read-only access.
- DNSSEC Checker
Check whether the domain's DNS answers are signed and validate.
- HTTP Security Headers Checker
Grade the security headers the site sends.
- Cloudflare WAF
How Cloudflare WAF rules work, and how Vigilbase sets them up and tunes them under change control.
Managed Cloudflare
Keep Cloudflare configured, monitored and improving. Vigilbase handles agreed changes and incident response, with Core, Priority and Critical coverage options.
Explore Managed CloudflareManaged SOC
Managed SOC on the security tools you already pay for. The Vigil agent investigates, our analysts handle exceptions, and coverage follows your SLA tier.
Explore Managed SOC