Hi good see you again @czeller,
OK, I assume that you’re mentioning about the front-end.
One possibility is that the issue you’re facing might be caused due to “UA string and qualification” in “Front-end target settings” section.
For example, you can find the default value bot:HOST
which means:
- When the user agent string includes “bot”,
- and also the host name can be fetched by the DNS reverse lookup,
- then the request is not blocked,
- even it comes from black listed countries.
And furthermore, if you uncheck “DNS reverse lookup“, this rule is considered as bot:*
which means if the user agent string includes “bot”, then the request is passed.
Please find some details in “UA string and Qualification“.
So I propose you to try one of the followings or both:
- Select “Unauthenticated user” at “Record validation logs” in “Record settings” section. You can find not only blocked but also passed in the logs. Then you can refine the rules in “UA string and qualification“.
- Make “UA string and qualification” empty. All the good bots such as google, yahoo, bing, facebook, twitter and etc come from US. So I think you don’t need the current rules.
I’d appreciate you if you give me some feed back.
Thanks.
P.S. I’ll add the new mode “Blocked / UA qualified” at “Record validation logs” in the next release to find those situations easily ??