Skip to content
Rebirth Mirrors — sponsored banner

Total Requests

0
This session

Live Requests

0
+0.0%Last 180s

Peak Requests

0
Last 180s

Avg Requests

0
Last 180s

Mitigation

Protected
No
Protection Type

Automated Access Detection

0

Automated00.0%
Likely automated00.0%
Likely human00.0%

Cloudflare Dstat — Live Passed / Bypassed / Blocked

Connecting…
https://c1.dstatbots.win/dstat
FAQ

Requests · Last 180s

0

About

What is a Cloudflare Dstat?

A Cloudflare Dstat monitors a target sitting behind Cloudflare's standard proxy (no active challenge). Unlike a plain request counter, it classifies every request into three buckets: passed 200 responses that reached the origin normally, requests that bypassed protection rules, and requests Cloudflare blocked at the edge.

Cloudflare Dstat FAQ

What do Passed, Bypassed and Blocked mean?

Passed (200) are requests that went through Cloudflare and got a normal response from the origin. Bypassed are requests that slipped past protection rules. Blocked are requests Cloudflare stopped at the edge — they never reached the origin.

Is there a UAM or CAPTCHA challenge on this endpoint?

No. This endpoint runs Cloudflare's standard proxy without an active challenge. For challenge-protected targets, see the Cloudflare UAM and Cloudflare CAPTCHA Dstat pages.

Why is the blocked share important?

A high blocked share means Cloudflare's edge is filtering most of the traffic before it reaches the origin — the method generates volume but little real impact. Effective Layer7 traffic shows a high passed/bypassed share instead.

Other Dstat Servers