Every anti-detect browser plays the same game: patch the JavaScript fingerprinting surface — randomize canvas, swap the WebGL renderer, rewrite the user-agent, fake the timezone. Against a fingerprinter that only reads JavaScript, it works. But a browser only controls its JavaScript. It doesn't control the network it connects over — the TLS handshake, the ASN, the protocol it negotiates, the IP it actually comes from. That's set by infrastructure, not by a patch. liarjs scores the contradictions between the two. A profile can look like a pristine Chrome in JavaScript and still be sitting on an IP whose timezone is twelve hours off, negotiating a handshake no real Chrome would send. Fake one layer; the other gives it up. See where your own browser contradicts itself → liarjs.dev

liar.js

How consistent is your browser, really?

How consistent is your browser, really?