Frequently Asked Questions
How does Cloudflare detect bots?
Cloudflare uses multiple methods to detect bots, but these vary by plan. For more details, refer to Plans.
How do I know what’s included in my plan?
To know what’s included in your plan, refer to our Plans.
How do I set up my bot product?
To learn how to set up your bot product, refer to Get started.
Yandex bot unexpectedly blocked by the WAF managed rule with id 100203
Yandex updates their bots very frequently, you may see more false positives while these changes are propagated. New and recently updated bots will occasionally be blocked by Cloudflare WAF managed rule with id 100203, as the IP list of Yandex bots has not yet synced with Yandex’s most recent changes.
- Disable the WAF managed rule with id 100203 temporarily,
- or create a firewall rule with the Bypass action to bypass WAF managed rules when a request is coming from the Yandex IP and the user-agent contains Yandex. Refer to our Firewall actions.
Once the new Yandex IP is propagated to our system, the requests won’t be blocked any more. This can take up to 48 hours. If you see any Yandex bots still being blocked after 48 hours with no change to the bot, please contact Cloudflare Support.
How does machine learning work?
Supervised machine learning takes certain variables (X) like gender and age and predicts another variable (Y) like income.
In Bot Management and Super Bot Fight Mode, the X variables are request features, while the Y variable represents the probability of solving a challenge based on X values.
Cloudflare uses data from millions of requests and re-train the system on a periodic basis. You can learn about this data from your own request logs such as Cloudflare Logpull and Logpush as well as the Firewall API.
Why am I seeing a Managed Challenge action for firewall rules?
When you choose to challenge different bot categories with Bot Fight Mode or Super Bot Fight Mode, you will see Firewall Events with an Action Taken of Managed Challenge.
You may also see Managed Challenge as a result of a firewall rule.
What is the difference between the threat score and bot management score?
The difference is significant:
- Threat score (cf.threat_score) is what Cloudflare uses to determine IP Reputation. It goes from 0 (good) to 100 (bad).
- Bot management score (cf.bot_management.score) is what Cloudflare uses in Bot Management to measure if the request is from a human or a script**.** The scores range from 1 (bot) to 99 (human). Lower scores indicate the request came from a script, API service, or an automated agent. Higher scores indicate that the request came from a human using a standard desktop or mobile web browser.
These fields are available via Cloudflare Firewall Rules.
What is cf.bot_management.verified_bot?
A request’s cf.bot_management.verified_bot value is a boolean indicating whether such request comes from a Cloudflare allowed bot.
Cloudflare has built an allowlist of good, automated bots, e.g. Google Search Engine, Pingdom, and more.
This allowlist is large based on reverse DNS verification, meaning that the IPs we allow really match the requesting service. In addition to this, Cloudflare uses multiple validation methods including ASN blocks and public lists. If none of these validation types are available for a customer, we use internal Cloudflare data and machine learning to identify legitimate IP addresses from good bots.
To allow traffic from good bots, use the Verified Bot field in your firewall rule.
I run a good bot and want for it to be added to the allowlist (cf.bot_management.verified_bot). What should I do?
Cloudflare maintains a sample list of verified bots in Cloudflare Radar.
As a bot operator, in order to be listed by Cloudflare as a Verified Bot, your bot must conform with our verified bot public policy. If your bot meets this criteria, submit this online application.
What information do I need to troubleshoot my bot issues?
If you are experiencing errors with your bot solution and need to submit a Support request, include the following information:
- IP addresses
- Firewall Rule IDs, rule expression, Challenge solve rates
- Common user-agents among false positives
- Common ASNs among false positives
- Screenshots of strange activity from the firewall, such as a huge spike in challenged traffic on the graph
- Problematic URIs or paths
- Rough description of how your domain is configured.
- Is one zone SSL for SaaS while the others are not?
- Is most API traffic sent to a particular URI?
- How much mobile traffic do you expect?
What should I do if I am getting False positives caused by Bot Fight Mode (BFM) or Super Bot Fight Mode (SBFM)?
How to disable BFM**/SBFM feature?**
If you encounter any issues with BFM/SBFM feature (e.g. false positive), you can disable it under Security > Bots.
- For Free plans, toggle the Bot Fight Mode option to Off
In parts of your site where you want bot traffic, you can use the
Skip action in Custom Rules to specify where Super Bot Fight Mode should not run.
To enable the
Skip action in Custom Rules, refer to the WAF documentation. Skip rules are only available to customers who have migrated from Firewall Rules to Custom Rules.
Super Bot Fight Mode feature (SBFM) is still blocking requests even though the feature is turned off, why?
This is a known issue the Bots team is working to resolve in the near future. In the meantime, there is a workaround to resolve such issue. You will need to run the following API command to check and remove the SBFM ruleset:
- List the existing Rulesets at the zone level
curl -X GET "https://api.cloudflare.com/client/v4/zones/zone_id/rulesets" \-H "X-Auth-Email: <EMAIL>" \-H "X-Auth-Key: <API_KEY>" \-H Content-Type: application/json
From the output in step 1, find the ruleset ID that is associated with the zone’s SBFM configuration. You should be able to see
"phase": "http_request_sbfm"for that ruleset.
Use the ruleset ID you found to delete the SBFM ruleset
curl -X DELETE "https://api.cloudflare.com/client/v4/zones/zone_id/rulesets/rulesets_id" \-H "X-Auth-Email: <EMAIL>" \-H "X-Auth-Key: <API_KEY>" \-H "Content-Type: application/json"
Note that you need to replace