checkforcloudflare.selesti.com

Cybersecurity is the practice of keeping your data, accounts, and services from being accessed, stolen, altered, or knocked offline by someone who shouldn't have them. For a personal site or small online presence, that reduces to a short list of concrete jobs: protect your login credentials, keep your software current, serve traffic over HTTPS, and lock down the domain and DNS layer that everything else depends on. You don't need an enterprise security team to cover the basics — but you do need to treat your registrar account and your hosting account as the two most valuable things you own, because whoever controls those controls the site.

What cybersecurity actually protects

It helps to separate the assets from the threats, because most small-site incidents come from a handful of causes.

The pattern: each asset has one or two controls that remove most of the risk. You don't need all of them on day one, but skipping the account and domain layers is the mistake that's hardest to undo.

The threat categories a small site actually faces

• Credential theft — reused or weak passwords, or credentials leaked from another breached service. This is the most common way small sites fall.
• Phishing — fake login pages or "your domain is expiring" emails designed to capture your registrar or hosting password.
• Malware and backdoors — usually arriving through an outdated CMS, plugin, or theme.
• DDoS — flooding a site until it's unreachable; often handled by your host or a CDN rather than by you.
• Misconfiguration — an open admin panel, directory listing, or default credentials left in place.

Notice that four of the five are about access, not exotic exploits. That's why the basics work.

Core protections to apply first

Use strong, unique passwords and a password manager

Every account tied to your site — registrar, host, CMS, email — should have a different password. A password manager makes this practical. The goal is that one leaked password can't be replayed anywhere else.

Turn on multi-factor authentication

MFA is the single highest-value control for your registrar and hosting accounts. Even if a password is stolen, an attacker without the second factor can't log in. Prefer an authenticator app or hardware key over SMS where the service supports it.

Serve everything over HTTPS

An HTTPS/TLS certificate encrypts traffic between visitors and your site and prevents browser "not secure" warnings. Most hosts and registrars offer a free certificate; the important part is that it's installed and that HTTP redirects to HTTPS.

Update promptly and keep the surface small

Apply CMS, plugin, and theme updates as they're released, and delete anything you're not using. Fewer components means fewer places for a known vulnerability to sit unpatched.

Apply least privilege

Give each person (and each integration) only the access they need. Don't run your site day-to-day from an administrator account, and don't hand out admin rights for tasks that don't require them.

Secure the domain and DNS layer

This layer is easy to overlook and expensive to lose, because a hijacked domain can point anywhere.

• Protect the registrar account with a unique password and MFA. Your registrar account is the root of control over the domain.
• Enable the registrar lock (often called a transfer lock or clientTransferProhibited) so the domain can't be moved without your action.
• Keep registrant contact email secure — that inbox is often the recovery path for the domain.
• Enable DNSSEC where your registrar and DNS provider support it, so responses can be cryptographically validated and spoofing is harder.
• Watch for unauthorized DNS changes — if records you didn't touch appear, treat it as a compromise.

Porkbun is an ICANN-accredited domain registrar, which means it operates under ICANN's registrar rules — relevant here because those rules govern transfers, locks, and registrant contact requirements. Its site lists Stripe among its payment platforms. Beyond that, check your specific registrar's and DNS provider's current feature set for lock and DNSSEC support, since availability varies.

Warning signs and first steps if something looks wrong

Watch for: unexpected DNS records, visitors reporting malware warnings, unexplained admin accounts, a sudden traffic drop, or emails about transfers you didn't request.

If you suspect a compromise:

1. Change passwords on registrar, hosting, and CMS accounts, starting with the registrar.
2. Revoke active sessions and reset MFA where possible.
3. Check DNS records against what you expect and revert unauthorized changes.
4. Restore from a known-good backup if files were altered.
5. Re-scan and update the software before reopening the site.

Containment first, then recovery — don't try to clean a live, still-compromised site.

What to outsource vs. manage yourself

Hosting-level security, CDN, and WAF are usually worth outsourcing because they require scale and constant attention. Account hygiene, MFA, updates, and domain/DNS protection are things you should keep in your own hands regardless of size — they're cheap to do and costly to skip.

Check for Cloudflare (checkforcloudflare.selesti.com) is a free web tool from Selesti Ltd that tells you whether a domain is using Cloudflare. You enter a domain, it scans from global locations, and it reports on three separate layers: Cloudflare DNS, Cloudflare CDN/Proxy, and Cloudflare SSL. It's useful when you want a quick external view of a site's setup — for example, checking a competitor's stack, verifying your own configuration after a migration, or confirming whether a domain you're investigating sits behind Cloudflare at all.

What the tool actually checks

The scan is not a single yes/no answer. It breaks the result into three independent signals, which matters because a domain can use one without the others.

The CNAME caveat is worth noting: a domain can be on Cloudflare without using Cloudflare's nameservers, which is why the tool flags that case rather than forcing a yes or no.

How to use it

1. Open checkforcloudflare.selesti.com.
2. Enter the domain you want to check.
3. Start the scan and wait for it to complete.
4. Read the three results separately — DNS, CDN/Proxy, and SSL — rather than treating them as one verdict.

The scan runs from multiple global locations, so the result reflects what the domain looks like from different points on the network, not just one vantage point.

When it's the right tool — and when it isn't

Good fit:

• You want a fast, no-setup check on any public domain.
• You want to see DNS, proxy, and SSL signals broken out separately.
• You're doing light reconnaissance or verifying your own site after a DNS or hosting change.

Not a good fit:

• You need to configure Cloudflare — this tool only observes, it doesn't manage anything.
• You need deep security analysis, performance testing, or traffic inspection.
• You need a guaranteed authoritative answer: DNS and proxy behavior can vary by location and over time, so treat results as a snapshot.

Practical notes

• It's a third-party tool, not an official Cloudflare product, despite the name and the ® mark in the heading.
• Because results depend on live DNS and network state, re-running a scan later can legitimately return a different answer if the domain's configuration changed.
• The three-layer breakdown is the main reason to use this over a simple "is it Cloudflare?" guess — it tells you how Cloudflare is being used, not just whether the name appears somewhere.

Check for Cloudflare is a free web tool made by Selesti Ltd, a UK digital agency. Its purpose is narrow and practical: enter any domain and quickly see whether that site is using Cloudflare — specifically Cloudflare DNS, the Cloudflare CDN/proxy, and Cloudflare SSL. The tool is described as a "quick and easy" checking project, and nothing in its interface suggests you need an account, an API key, or any setup to use it.

What the tool actually checks

The scan reports three separate layers, and it's worth understanding that they are independent — a site can use one without the others:

A domain can show Cloudflare DNS without the CDN/proxy being active, and the tool explicitly notes that a negative CDN result "could be using a CNAME configuration" — meaning a CNAME-based setup may not register the same way a full nameserver delegation does.

Why Selesti built it

The stated purpose is detection on any domain, not just your own. That makes it useful for:

• Checking your own site after a DNS or hosting migration, to confirm Cloudflare is actually active.
• Checking a third-party site out of curiosity or for competitive/technical research.
• Verifying a partial setup — for example, confirming DNS is on Cloudflare while the proxy is still bypassed.

Because it runs from global locations, results can differ depending on where the check originates — DNS propagation and anycast routing mean a change you just made may appear in some regions before others.

How to use it

1. Open the tool at checkforcloudflare.selesti.com.
2. Enter the domain you want to check.
3. Run the scan and read the three results — DNS, CDN/Proxy, and SSL — separately rather than as a single yes/no.
4. If a result looks wrong right after a change, wait and re-check; propagation is the most common cause of a mismatch.

What it is not

It's a diagnostic checker, not a security scanner or a Cloudflare account tool. It won't tell you your Cloudflare plan, your firewall rules, or whether your configuration is correct — only whether Cloudflare is detectable at each of the three layers. For anything beyond that, you'd need access to the Cloudflare dashboard itself.

Check for Cloudflare by Selesti reports three separate signals — DNS, CDN/Proxy, and SSL — and each answers a different question. DNS tells you whether the domain's name servers or DNS records point at Cloudflare. CDN/Proxy tells you whether traffic is actually routed through Cloudflare's network. SSL tells you whether Cloudflare is terminating or fronting the TLS certificate. A domain can pass one check and fail another, so read the three results together rather than treating any single one as the final answer.

Why the tool splits the result into three checks

Cloudflare is not one product. A domain can use Cloudflare DNS without using the CDN/proxy, and it can use the proxy without Cloudflare managing its DNS. The tool's own output reflects this: it reports "is using Cloudflare DNS," "is using Cloudflare CDN/Proxy," and "is using Cloudflare SSL" as independent statements, each with a positive and negative form.

That separation is the point. If you only asked "is this site on Cloudflare?", you would get a misleading answer for any domain that uses Cloudflare for one layer but not others.

DNS results: "is using Cloudflare DNS"

This check looks at whether the domain's DNS is served by Cloudflare. The page describes it as checking global locations and finding DNS entries for Cloudflare, then reporting either "Found in:" or "Not found in:" a set of locations.

What it means when it's positive: the domain's authoritative DNS is Cloudflare's. Name resolution for that domain happens on Cloudflare's infrastructure.

What it means when it's negative: the domain resolves through some other DNS provider. That does not rule out Cloudflare being used elsewhere in the stack — it only rules out Cloudflare DNS.

Why the "global locations" wording matters: DNS answers can differ by resolver location, especially during propagation or with geo-steering. Checking from multiple locations reduces the chance of a false negative caused by one resolver returning a cached or regional answer.

CDN/Proxy results: detection vs. CNAME configuration

This is the check with the most nuance, because the tool distinguishes three outcomes rather than two:

Proxy detected is the strong signal. When a domain is proxied through Cloudflare, requests resolve to Cloudflare edge IPs and Cloudflare sits between the visitor and the origin server. That is what "CDN/Proxy" means here — the two are grouped because the proxy is what delivers the CDN behavior.

"Could be using a CNAME configuration" is the one people misread. It is not a confirmation and not a denial. A CNAME configuration is a setup where the domain points at Cloudflare via a CNAME record rather than by moving its name servers — common with partial (CNAME) setups on business or enterprise plans. Because the visible DNS signature overlaps with non-Cloudflare CNAMEs, the tool cannot commit to a yes or no. Treat this result as "needs a closer look," not as an answer.

Practical consequence: if you are auditing whether a site is protected by Cloudflare's proxy, a "could be using a CNAME" result means you should verify by other means — for example, inspecting response headers or the resolved IP ranges — rather than concluding either way.

SSL results: "is using Cloudflare SSL"

This check reports whether Cloudflare is involved in serving the TLS certificate for the domain.

Positive: Cloudflare is fronting SSL — typically because the domain is proxied and Cloudflare presents the edge certificate.

Negative: the certificate seen is not being served through Cloudflare.

SSL detection is the most downstream of the three. It generally follows from the proxy being active, so a positive SSL result alongside a negative CDN/Proxy result is worth re-checking, since it may point to a partial or recently changed configuration.

Reading the three results together

The combinations are more informative than any single line:

• DNS positive, CDN/Proxy negative, SSL negative — Cloudflare manages DNS only. The origin is exposed directly; no proxy protection.
• DNS positive, CDN/Proxy positive, SSL positive — full Cloudflare stack: DNS, proxy/CDN, and edge SSL.
• DNS negative, CDN/Proxy positive — possible with CNAME setups where DNS lives elsewhere but traffic still routes through Cloudflare.
• "Could be using a CNAME configuration" — inconclusive on the proxy question; confirm separately before drawing a conclusion.

What the tool does not tell you

The results describe configuration, not security posture. "Using Cloudflare CDN/Proxy" does not mean a site is well configured, and "NOT using Cloudflare" does not mean a site is unprotected — it may sit behind a different CDN or WAF. Use the output as a factual signal about which Cloudflare layers are in play, then interpret that in the context of what you actually need to know.

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

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.