Research & deep-dives
How bot detection actually works, what makes a browser identifiable, and how we build against it — written up in the open, vendor-neutral, and reproducible.
Every research article and Q&A term, connected. Also on the Q&A hub.
Coherence over camouflage: why a plausible identity beats a hidden one
Most stealth tooling tries to hide. The signals that survive scrutiny don't hide — they agree with each other.
All articles
Spec invariants as lie detectors
Many web APIs are not free-form — the spec or the engine constrains their values, so a reading can be convicted by the API's own rules, with no baseline and no population data.
Identifying the engine behind the User-Agent
A User-Agent is a claim. The JavaScript engine underneath answers independently — and it cannot easily be made to lie.
Cross-realm coherence: why a worker must agree with the page
A page is not one JavaScript realm but several — and the values they report about the same machine have to match.
How browser stealth is measured: coherence, entropy, and headless tells
What consistency testers, entropy tools, and headless benchmarks actually measure — and why a 'unique' fingerprint and a 'detectable' one are different problems.
Patches, not black boxes: how a stealth browser is built and verified
How an anti-detect Chromium is assembled from readable patches, built reproducibly, and verified end-to-end — so you can trust the binary matches the source.
How automation gets caught, layer by layer
From the WebDriver flag to the TLS handshake — the distinct layers a detector reads, and why fixing one rarely helps.
Anatomy of a browser fingerprint: every signal, and why they must agree
A field guide to the signals that make a browser identifiable — grouped by where they come from and how they betray a spoof.
Coherence over camouflage: why a plausible identity beats a hidden one
Most stealth tooling tries to hide. The signals that survive scrutiny don't hide — they agree with each other.
Topics
Design principles
1 articleThe ideas that shape how Clearcote is built — and why.
Fingerprinting
3 articlesDeep-dives into the signals that identify a browser, and how to keep them coherent.
Detection teardowns
2 articlesHow automation gets caught — layer by layer, from the driver to the network.
Engineering
1 articleHow the browser is patched, built and verified, in the open.
Benchmarks
1 articleReproducible tests: what we measure, how, and the numbers.
Fingerprint test references
Fingerprint check reference
Every check, grouped by browser subsystem, with the expected result and resolution.
Read referenceMethodology, scoring & limits
How coherence is measured, which evidence is scored, and what a public page cannot prove.
Read referenceDetection research & sources
The public detector artifacts and research behind the audit's signal attributions.
Read referenceLooking for shorter, direct answers? Browse the Q&A.