Pixelscan alternative: see why a browser looks inconsistent
Pixelscan is a popular free checker that tells you whether a browser setup looks consistent and whether it shows signs of a bot or a proxy. SpoofLens answers the same core question with a different focus: every finding comes with an explanation, privacy protection is kept apart from spoofing, and the same checks are being turned into an API for website owners.
| Pixelscan | SpoofLens | |
|---|---|---|
| Sign-up | Not needed | Not needed |
| Consistency check | Yes | Yes, more than 30 rules |
| Bot and automation signs | Yes | Yes: WebDriver, headless traces, replaced built-in functions |
| Network checks | Proxy check, IP blacklist, DNS leak | Data center or VPN network, Tor exit, proxy headers, time zone vs IP; blacklist check on My IP |
| DNS leak test | Yes | Not yet |
| Price | Free | Free; Pro and Business plans are coming |
Check your browser right now
Checking your browser…
What Pixelscan checks
Pixelscan runs a set of tests in one go: fingerprint signals such as canvas, audio, fonts, WebGL and HTTP headers; consistency between them, for example a Windows User-Agent with macOS hardware signals, or a time zone and language that do not match the IP location; traces of headless browsers and automation; and network checks, including an IP blacklist lookup, a DNS leak test and a proxy checker. It presents the result as the way your setup looks to anti-fraud systems.
How SpoofLens approaches the same question
We also start from consistency, because that is how anti-fraud systems catch spoofed browsers: not by one odd value but by two values that cannot both be true. Beyond the obvious pairs (User-Agent and platform, time zone and IP country, languages in the headers and in JavaScript), SpoofLens compares the page with a Web Worker and an invisible iframe, checks whether built-in browser functions were replaced by scripts, compares the Client Hints sent in HTTP headers with the ones JavaScript reports, and draws the same canvas and audio fingerprints twice to catch injected noise.
Each finding has a level (contradiction, suspicious, weak signal) and a plain-language explanation of what it means and what innocent causes it can have. A VPN, a corporate network or a laptop with two graphics cards can trigger some of them, and the page says so.
Privacy browsers are not treated as fakes
Brave, Firefox with resistFingerprinting and Tor Browser change some values on purpose so that sites cannot track you. A plain consistency checker can mistake those changes for spoofing. SpoofLens recognises these browsers and shows their changes as privacy protection, which does not lower the truth index.
What SpoofLens does not do yet
- No DNS leak test yet.
- No TLS, HTTP/2 or TCP fingerprinting yet. These need dedicated server-side capture and are planned.
- No saved history or profile comparison yet. Both are part of the upcoming Pro plan.
Who SpoofLens is for
Developers and QA engineers who need to know how a browser presents itself, website owners who want to tell real visitors from bots and spoofed browsers, and anyone who wants to know what their browser reveals. We explain how detection works; we do not publish guides on getting past anti-fraud checks.
Frequently asked questions
- Is SpoofLens free?
- Yes. The full browser check, the IP and anonymity page and 16 website tools are free and need no account. Paid plans for profile comparison and a website API are in preparation.
- Does SpoofLens store my fingerprint?
- No. The signals are sent to our server once for the cross-check and are not saved. Only the daily number of checks is counted.
- Is SpoofLens affiliated with Pixelscan?
- No. Pixelscan is an independent service. This comparison is based on what it describes publicly.
Read next
- BrowserLeaks alternative: one check that explains what it finds
- Whoer alternative: your IP, anonymity and browser in two checks
- CreepJS alternative: the same kind of lie detection, explained
- Browser fingerprinting: what it is and how it works
- How websites detect bots and automated browsers
- Canvas, WebGL and audio fingerprints: how they work