botcheck
Does your browser look automated?
The checks run entirely in your browser and nothing is sent: your taps, clicks, typing and results never leave the page. It looks for signs of automation in your browser's environment and in how your taps, clicks and mouse movements arrive.
Checks
Touch test
On a phone or tablet, tap the box about 20 times at your own pace. With a mouse, move around and click the choices, links and button below: the mouse checks run on those.
The checks above update after each tap.
Try a few actions
Fill in the form, tap the choices and links, open a panel. What you type is never read, kept or sent: only the kind of key (letter, delete, keyboard suggestion) is counted.
How it works
Touch signals
When a finger rests on glass, the phone keeps reporting it even when it does not move, and it samples the finger faster than the screen redraws, so the browser bundles several samples into each movement. Pressure varies from tap to tap. Scripted touches often send a fixed pressure, skip the resting samples, carry one sample per movement or arrive late. Each of these is a separate rule, shown with its limits when it fires.
Environment signals
Some automation announces itself: the navigator.webdriver flag, a "HeadlessChrome" user agent, a software graphics renderer, an empty language list, a window with no size, or a platform that disagrees with the browser's own client hints. These are general heuristics, not fitted to data, and some real setups trigger them too.
What this page cannot tell
It cannot prove you are a person, and it can be wrong. The touch rules were set from one participant on one phone, so other devices, assistive input and hardware keyboards can trigger them. It uses no IP address, network fingerprint or reputation from other sites, which large bot-protection services rely on. Nothing you do here is sent anywhere.