How to Check if a Domain Is Using Cloudflare with Check for Cloudflare

Updated

Check for Cloudflare (checkforcloudflare.selesti.com) by Selesti is a free browser tool that scans a domain and reports whether it uses Cloudflare DNS, Cloudflare CDN/Proxy, and Cloudflare SSL. You only need the domain name — no account or login is mentioned on the site. It's useful when you want a quick, three-part answer about a domain's Cloudflare footprint without running your own DNS or HTTP lookups.

What the tool checks

The page runs a scan and returns three separate findings, each with its own "using" or "not using" verdict:

  • Cloudflare DNS — whether the domain's DNS entries point to Cloudflare. The results show which global locations were checked and list where Cloudflare entries were Found in and Not found in.
  • Cloudflare CDN/Proxy — whether traffic is routed through Cloudflare's proxy.
  • Cloudflare SSL — whether Cloudflare's SSL is in use.

Because these are reported independently, a domain can show Cloudflare DNS but not Cloudflare CDN/Proxy, or vice versa. That distinction matters when you're diagnosing how a site is set up.

How to run a check

  1. Open checkforcloudflare.selesti.com in your browser.
  2. Enter the domain you want to scan (for example, the site you're auditing or a competitor's).
  3. Start the scan. The page shows a "Scanning…" state while it checks global locations.
  4. Wait for the results to load, then read the three sections: DNS, CDN/Proxy, and SSL.

Expected result: each section states whether the domain is or is NOT using that Cloudflare service, with the DNS section also listing the locations where Cloudflare entries were found or not found.

Reading the results

Finding What it means
"is using Cloudflare DNS" DNS entries for Cloudflare were found in the checked global locations.
"is NOT using Cloudflare DNS" No Cloudflare DNS entries were found.
"could be using a CNAME configuration" A CNAME setup may be in play, so the DNS result isn't a clean yes/no.
"is using Cloudflare CDN/Proxy" Traffic appears to route through Cloudflare's proxy.
"is NOT using Cloudflare CDN/Proxy" No Cloudflare proxying detected.
"is using Cloudflare SSL" / "is NOT using Cloudflare SSL" Whether Cloudflare SSL is in use.

The CNAME note

If you see "could be using a CNAME configuration," treat the DNS result as inconclusive rather than a firm "no." A CNAME setup can hide the direct Cloudflare DNS signature, so the tool flags it instead of declaring the domain Cloudflare-free.

Common snags

  • Mixed verdicts are normal. DNS, CDN/Proxy, and SSL are separate checks. Don't assume one result determines the others.
  • "Not found in" some locations doesn't always mean "not using." The DNS section reports per-location findings; read the overall verdict alongside the location lists.
  • A CNAME result needs a second look. If the tool says a CNAME configuration is possible, verify with another method before concluding the domain doesn't use Cloudflare.

When to use it

Reach for this tool when you want a fast, no-setup read on whether a domain leans on Cloudflare — for example, checking your own site after a DNS or proxy change, or sizing up how another site is hosted. For deeper diagnostics (specific records, headers, or performance), you'll still want dedicated DNS and HTTP tooling; this tool gives you the quick three-part signal first.