CAPTCHA measurement: what each CAPTCHA's own server thinks of your browser
Real CAPTCHAs, our own keys, one page. Each one hands its answer to its own vendor's server, and you see the verdict we record.
Some test keys. CAPTCHAs marked "test key" still use the vendor's test key: they always pass and measure nothing. Their real keys are on the way.
reCAPTCHA v3 invisible score
Google scores the visit from 0.0 (likely a bot) to 1.0 (likely a human) without showing a puzzle.
waiting…
reCAPTCHA v2 tick box
The "I'm not a robot" box. It passes on a tick or asks for a picture puzzle.
waiting…
Cloudflare Turnstile managed
Usually passes without any click. We note whether it had to ask you to interact.
waiting…
ALTCHA open source, proof of work
Self-hosted. Your browser does a small amount of computing to prove it is willing to spend effort.
waiting…
Cap open source, proof of work
Self-hosted, with extra checks on the browser itself.
waiting…
Your browser, as the page sees it
What we record
- One line per check: which CAPTCHA, the vendor's verdict, score and error codes, how old the token was, how long it took, and whether it asked you to interact.
- Your browser's user agent, the signals in the table above, and the country Cloudflare reports. No IP address, and no cookie of ours. Google and Cloudflare set their own cookies inside their widgets.
- Why: to measure, over time and in the open, how CAPTCHAs judge browsers and AI agents. Nothing here is sold, and we run no CAPTCHA-solving service.