Check guide ยท On the wire
Managed bot score
Cloudflare's own bot score for this exact request.
What this check is
Sites behind Cloudflare's bot management get a score for every request, from 1 (certainly a bot) to 99 (certainly human), computed from Cloudflare's network wide view of the traffic. This check reports that score for the request that loaded this page, when the plan this site runs on exposes it. It is the one row in the table Tells does not compute itself.
What Tells reads
- The managed bot score Cloudflare assigned to the request
- Whether Cloudflare identifies the request as a verified bot (a known, declared crawler)
How to read your result
- Fail: A score under 30, or the request is identified as verified bot traffic.
- Warning: A score from 30 to 49: the borderline band.
- Pass: A score of 50 or better.
- Not available: Cloudflare Bot Management is not active on this site, so there is no real score to show. The row says so rather than guessing.
Why it matters
This is the closest thing on the page to ground truth, because it is an actual production gate's opinion rather than a reconstruction of one. A browser setup that reads clean on every self-reported signal can still score badly here if its traffic pattern resembles automation at network scale, which is exactly the gap that surprises people.
Where this matters most
Across the platforms Blowhorn works with, rated in the platform guide (H = matters a lot, M = contributes, L = no public evidence; tags mark vendor-stated, reported, or inferred evidence):
- LinkedIn (M): no Cloudflare-style gate is public, but a managed bot-defence element is reported in its pages [Reported]
- X (M): Arkose provides managed risk scoring and challenges at key gates [Reported]
- Reddit (M): an edge network-security layer scores unauthenticated traffic before login [Inference]
Everywhere else in the set this one rates Low.
In your report
Find it in the checks table on the tool page, with the detail in
the Server / IP section. The same findings appear in the
report JSON under verdict.reasons, and the agent guide explains
how to read them programmatically.