Edge vs Origin Check

Enter a domain and see which layer answers a probe path: a CDN or provider block page, the origin refusing, or nothing at all — plus whether a CDN sits in front. We make a few requests from our server (SSRF-guarded); the domain is not stored.

This is the check that follows a real observation: refusing scanner traffic at the origin keeps the figures high, because the counter measures what reaches the server. If a probe path is refused before it arrives, that is a different layer — and it is worth knowing which one is doing the work.

What it reports

• Per path. Status code, which layer answered, the server header, and the evidence found — provider block markers, cf-mitigated, a ray ID, or none of those.
• The front. Whether response headers show a CDN in front (Cloudflare, CloudFront, Sucuri, Akamai) or nothing observable.
• The paths. Credential files, framework endpoints and the scanner patterns we see in our own logs — the same set our firewall refuses.

What it cannot tell you

• It cannot say which rule fired inside a provider. That is not observable from outside; the layer is.
• It cannot attribute a refusal to a policy you wrote. A provider may block a path you never mentioned.
• Its answers depend on the user agent: we send a browser-like one, and providers may treat a crawler differently.
• It cannot tell you whether search or AI engines can cite you — for access, use the Robots.txt AI Access Check.

Frequently asked questions

How is this different from your other tools?

The browser-only tools never contact your site. This one does: a handful of requests from our server to the domain you enter. We do not store the domain or the results, and a per-IP rate limit keeps it cheap.

Can it tell me which rule blocked a request?

No. You can see which layer answered and what evidence the response carries; providers do not expose their internal rule matching to the public internet.

Why do results depend on the user agent?

Providers and origins may answer different clients differently. We send a browser-like agent so the result matches a visitor's browser; a crawler agent can legitimately see something else.

Does edge blocking help SEO?

It helps operations rather than rankings: noise never reaches the server, logs stay readable, refusals cost less. It does not by itself change how search or AI engines treat your pages.

If you want the reasoning behind this

We wrote down what happened when we moved our own scanner blocking from the origin to the edge, including what we deliberately refused to do (no country blocking, no blanket bot challenges) and how this page's numbers are published. It is in the article on that change.