Frequently Asked Questions

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 a Cloudflare WAF managed rule, as the IP list of Yandex bots has not yet synced with Yandex’s most recent changes.

Workarounds:

• Create an exception to temporarily skip the managed rule with ID …f6cbb163  when a request is coming from the Yandex IP and the user-agent contains Yandex.
• Create a WAF custom rule with the Skip action to temporarily bypass WAF Managed Rules when a request is coming from the Yandex IP and the user-agent contains Yandex.

If you are using the legacy WAF managed rules (now deprecated), disable the WAF managed rule with ID 100203 temporarily.

Solution:

Once the new Yandex IP is propagated to our system, the requests will not be blocked anymore and you can remove any workaround you configured. 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, contact Cloudflare Support.

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.

When you choose to challenge different bot categories with Bot Fight Mode or Super Bot Fight Mode, you will see Security Events with an Action Taken of Managed Challenge.

You may also see Managed Challenge due to a triggered WAF custom rule.

This does not mean that your traffic was blocked. It is the challenge sent to your user to determine whether they are likely human or likely bot.

To understand if the result of the challenge was a success or a failure, you can verify using Logpush.

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 WAF custom rules and other products based on the Ruleset Engine.

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 WAF custom rule.

The JA3 Fingerprint can be null or empty in some cases. The most common case is for HTTP requests, because JA3 is calculated in TLS, but can also be empty due to the following:

• Orange to Orange zones (Cloudflare Zone proxied to another Cloudflare Zone).

• Worker sending requests within the same zone or to a zone that is not proxied (or a 3rd party).

Cloudflare maintains a sample list of verified bots in Cloudflare Radar Open external link .

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 Open external link .

If you are experiencing errors with your bot solution and need to submit a Support request, include the following information:

• RayIDs
• IP addresses
• WAF custom rule IDs, rule expression, Challenge solve rates
• Common user-agents among false positives
• Common ASNs among false positives
• Screenshots of strange activity from the WAF, 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 Cloudflare for SaaS while the others are not?
  • Is most API traffic sent to a particular URI?
  • How much mobile traffic do you expect?

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
• For Pro plans, click the Configure Super Bot Fight Mode link and set each of Definitely automated and Verified bots features to Allow, and toggle the Static resource protection and JavaScript Detections options to Off
• For Business and Enterprise (with no Bot Management add-on) plans, click the Configure Super Bot Fight Mode link and set each of Definitely automated, Likely automated and Verified bots features to Allow, and toggle the Static resource protection and JavaScript Detections options to Off

In parts of your site where you want bot traffic, you can use the Skip action in WAF custom rules to specify where Super Bot Fight Mode should not run.

You can use the Rules language and its operators and fields in custom rules to configure a scoped rule for approved automated traffic in Super Bot Fight Mode.

You cannot bypass or skip Bot Fight Mode using the Skip action in WAF custom rules or using Page Rules. Skip, Bypass, and Allow actions apply to rules or rulesets running on the Ruleset Engine. While Super Bot Fight Mode rules are implemented in the Ruleset Engine, Bot Fight Mode checks are not. This is why you can skip Super Bot Fight Mode, but not Bot Fight Mode. If you need to skip Bot Fight Mode, consider using Super Bot Fight Mode.

Bot Fight Mode can still trigger if you have IP Access rules, but it cannot trigger if an IP Access rule matches the request. For example, the IP Access rule matches the connecting IP.

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:

1. List the existing Rulesets at the zone level

curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets" \
--header "X-Auth-Email: <EMAIL>" \
--header "X-Auth-Key: <API_KEY>"

2. 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 "kind": "zone" and "phase": "http_request_sbfm" for that ruleset.

3. Use the ruleset ID you found to delete the SBFM ruleset.

curl --request DELETE "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets/{ruleset_id}" \
--header "X-Auth-Email: <EMAIL>" \
--header "X-Auth-Key: <API_KEY>"

Note that you need to replace <API_KEY> with your own API key.