Made in GermanyISO 27001 certification in progress

Free checks · No sign-up · Nothing stored

Bot Detection Test

Three answers: a normal browser, a privacy browser, or a browser a program is driving. The signal that decided it is named.

What this test does that others don't

  • Other testers: Brave, Tor, and Firefox resist mode scored as bots.

    This test: Three answers: normal, privacy browser, automation.

  • Other testers: A debugger trap that freezes the tab when DevTools is open.

    This test: No DevTools timing. The tab stays usable.

  • Other testers: A bot score with no reason.

    This test: The signal that decided it is named.

Checking

Reading the automation flag.

DevTools is not timed, and a privacy browser is not scored as a bot.

Questions people actually ask

Why do privacy browsers fail bot tests?

A lot of tests treat a coarsened fingerprint as automation. Brave, Firefox with fingerprint resistance, and Tor look different on purpose. This page keeps that separate from a browser that says it is being driven.

Does an open DevTools window count?

No. Timing tricks that watch the debugger freeze the tab and flag anyone with DevTools open. This test does not do that.

What is navigator.webdriver?

A flag the browser sets when a program such as a test runner is controlling it. When it is true, the browser itself is reporting automation. This page reads the flag. It does not explain how to hide it.

Country and network names come from DB-IP, used under CC BY 4.0.