2 min read
As discussed previously, all requests to Cloudflare’s network pass through our bot detection engines.
Cloudflare uses this information to surface different signals to help you identify the true origin of a request.
A bot score is a score from 1 to 99 that indicates how likely that request came from a bot.
For example, a score of 1 means Cloudflare is quite certain the request was automated, while a score of 99 means Cloudflare is quite certain the request came from a human.
The following table groups these scores into general buckets.
|Not computed||Bot scores of 0.|
|Automated||Bot scores of 1.|
|Likely automated||Bot scores of 2 through 29.|
|Likely human||Bot scores of 30 through 99.|
|Verified bot||Non-malicious automated traffic (used to power search engines and other applications).|
Bot Tags provide more detail about why Cloudflare assigned a bot score to a request.
The following values are examples of what may be present in the
BotTags log field, but not an exhaustive list:
Detection IDs are fields used to identify the specific detection that caused Cloudflare to identify traffic as bot traffic. If you are having an issue with one of our heuristics, this feature allows you to decide which heuristics to enforce on your zones with a default configuration.
A JA3 Fingerprint helps you profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
Cloudflare maintains an internal list of Verified Bots that are associated with search engine optimization (SEO), website monitoring, and more.
You can use this list to prevent any bot protection measures from impacting otherwise helpful bots, such as search crawlers.
For a partial list of verified bots, refer to Cloudflare Radar.
Unit 1 of 5