liarjs.dev

Privacy & disclaimer

The scan reads a lot about your browser to do its job, so here is exactly what happens to it, and what the numbers do and don't mean.

Last updated: July 2026

Privacy policy

What the scan reads

To measure consistency, the site processes two kinds of signals:

  • Browser signals read in JavaScript on your device: canvas, WebGL, WebGPU, audio, installed fonts, navigator properties, screen metrics and WebRTC.
  • Network signals that Cloudflare derives from your connection: approximate location, ASN, edge colo and TLS/client-hello characteristics, exposed to the edge viarequest.cf.

What we do with it

The result is computed and shown to you, and that's it. We do not store your scan. There is no user database, no account and no history: the browser signals stay in your browser, the network signals are used to render your page at the edge and are not persisted by us.

Cookies & analytics

The site does not use tracking cookies. We keep aggregate, cookieless traffic counts through a self-hosted, privacy-focused analytics endpoint (Counterscale) that records anonymous page-view data only: no cross-site profile is built. Static assets and fonts may be served through standard CDNs.

Third parties

  • Cloudflare: hosting and edge runtime; sees your request as any host would.
  • Self-hosted analytics: anonymous, aggregate page views only.

These providers process requests on our behalf; we don't sell or share your data with anyone.

Disclaimer

liarjs.dev is provided for educational and self-testing purposes, as-is and without warranty of any kind. Use it on browsers and connections you are authorized to test.

  • Results are indicative, not authoritative. A clean score does not guarantee you won't be flagged, and a flagged score does not mean you will be blocked; on real targets, proxy quality, account age and behavior dominate the outcome.
  • Fingerprinting and anti-detect are a moving target. Signals, heuristics and the leaderboard drift over time. A scored row on the leaderboard is one dated scan of one build on one host, kept with its screenshot - not a live measurement, and not a claim about every version of that product. Rows with no screenshot carry no score at all.
  • Nothing here is legal advice or an endorsement of evading detection systems you don't own or aren't permitted to test.

Contact

Privacy questions, corrections or takedown requests: