botcheck
A small library that checks whether a browser's story about itself adds up.
This browser
checking
Running the checks.
What stood out
- Nothing yet.
Add your behaviour
Click or tap both buttons and type a few words, then run the checks again. Only counts and timings are measured — never what you type.
Raw result
Every value the checks read
What it checks
Catching a bot red-handed is the easy part. The interesting part is that a browser describes itself in a dozen places, and a spoofed one rarely keeps all of them straight.
- Automation markers. navigator.webdriver, Selenium and Playwright leftovers, headless user agents.
- User agent against the browser. The claimed engine, platform and client hints, compared with how the engine really behaves.
- GPU. Software renderers, and renderers that don't exist on the claimed operating system.
- Math. Since Chrome 148 the last bit of Math.tanh depends on the operating system's math library.
- CPU. The sign bit of a hardware NaN and a 172-byte WebAssembly module tell x86 from ARM.
- Tampering. Native functions that were replaced, and canvas pixels that don't read back as drawn.
- Other contexts. The same values, read again inside an iframe and a worker.
- Behaviour. Pointers that jump instead of travelling, perfectly straight paths, impossibly even typing.
Use it
One file, no dependencies. Download botcheck.js and import it as a module.
import { detect, observe } from './botcheck.js';
const session = observe(); // start watching input, as early as possible
form.addEventListener('submit', async () => {
const result = await detect({ behavior: session });
result.verdict; // 'clean' | 'suspicious' | 'bot'
result.score; // 0 to 1
result.flags; // [{ id, weight, detail }]
}); Limits
Everything here runs on a machine the visitor controls, so a determined bot can fake all of it. The aim is to make faking expensive. It never sees clients that don't run JavaScript, and so far it has only been verified on Chrome 153 on Linux — the weights and reference values still need calibrating on other browsers. Treat the verdict as a signal, not a decision.
Nothing leaves this page. The checks run locally, nothing is stored, and no identifier is created.