Bot Detection Test
This test runs 10 client-side checks for automation-related browser properties, including WebDriver flags, injected globals, and API inconsistencies. The score is a local heuristic, not a probability or proof that a visitor is human or automated. It does not measure mouse movements or other interaction behavior.
What Is Bot Detection?
Bot detection estimates whether software controls a browser session using signals such as automation flags and injected JavaScript properties. Signals can be absent in automated browsers or present in ordinary browsers, so a test cannot reliably identify the operator from these properties alone.
How Does This Test Work?
We run 10 client-side checks for WebDriver flags, ChromeDriver properties, Selenium globals, and API inconsistencies. Plugin counts, language lists, memory, and processor values are weaker contextual signals. Each triggered check adds a fixed weight; those weights are not measured detection rates. Modern headless Chrome shares browser code with ordinary Chrome, and an empty plugin list can be normal. See the Chrome headless documentation and navigator.plugins documentation.
Why Does Bot Detection Matter?
- Websites use bot detection to block scrapers, credential stuffers, and DDoS attacks.
- Privacy tools sometimes trigger false positives - this test helps you check.
- Developers can verify that their automation frameworks are properly configured.
- Security researchers can evaluate anti-bot evasion techniques.
Related Tools & Guides
- Browser Fingerprint Lab - see your full fingerprint, which is often used alongside bot detection.
- HTTP Headers Inspector - bots often have distinctive header patterns.
- WebRTC Leak Test - inspect WebRTC address exposure separately from automation signals.
- Privacy Browser Settings - understand browser controls and their privacy tradeoffs.
Frequently Asked Questions
Why does my browser show a non-zero bot score?
Browser privacy controls, unavailable APIs, and ordinary device settings can trigger these checks. Review the listed observations; no calibrated score range establishes normal use or proves automation for every browser.
What is WebDriver detection?
WebDriver is a browser automation standard used by tools such as Selenium. Cooperative browsers can report automation through navigator.webdriver set to true under documented automation settings. Its absence does not prove human control. Puppeteer normally uses browser debugging protocols rather than WebDriver. See the browser documentation.
Can bots evade this detection?
Automated browsers can change or suppress some indicators, and ordinary browsers can trigger others. Our full scan at /scan adds TLS and TCP observations, but neither test guarantees detection or proves that a visitor is human.