# Block Threat {% hint style="info" %} This feature will increase the user verification attempt count. {% endhint %} Most legitimate browsers will score 1 or 2, indicating little risk. Most bots will score 4 or 5, indicating a concrete risk of automation backed by hard signals. Browsers that score 3 are ambiguous: no definitive automation signals, but an elevated (not conclusive) risk. Typical cases include legacy browsers/OS versions and other heuristic red flags.

### Bot Score Description * 5 (Bot): High confidence; strongly suggests automation. * 4 (Bot): Medium confidence; environment suggests automation. * 3 (Human): Low confidence; environment is ambiguous. * 2 (Human): Medium confidence; likely human. * 1 (Human): High confidence; user is probably a human. ### Usage Recommendations #### Low-Risk Servers * Blocking Criteria: Block users with a `Bot Score` of 5. * Rationale: This conservative approach minimizes the risk of falsely blocking legitimate users—even if the browser environment is otherwise rather suspicious. #### Standard Servers * Blocking Criteria: Block users with a `Bot Score` of 4 or higher. * Rationale: This is the recommended option for most servers, only blocking the most suspicious browsers with little cross over with real humans. #### High-Risk Servers * Blocking Criteria: Block users with a `Bot Score` of 3 or higher. * Rationale: This setting strikes a balance by targeting higher-risk environments while accepting a higher chance of false positives, particularly from users with older or unusual browsers or devices. #### Very High-Risk Servers * Blocking Criteria: Block users with a `Bot Score` of 2 or higher. * Rationale: This aggressive policy is designed for environments with strong security requirements. It targets any even remotely suspicious browser with high levels of false positives. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.authenticateme.xyz/en/owners-manual/setup/005-subpage/block-threat.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.