Pixelscan's consistent or inconsistent verdict compares pairs of browser and network signals. Here is what they are, and why green is not anonymity.
Search for "pixelscan" and the people arriving are rarely casual. Most have just seen a red "inconsistent" verdict on a browser setup they thought was in order, and they want to know what the tool is actually complaining about. That is a fair question, and it has a clear answer: the verdict is not a measure of how unique you are. It is a check on whether the things your browser says about itself agree with each other and with the network connection carrying them.
Key Takeaways
- Pixelscan is a free checker that reports whether your browser and network signals are consistent. Its private scoring weights are not published, so treat any description of them, including this one, as general rather than exact.
- A consistency check compares pairs of claims: the OS and browser you announce versus the engine actually running, timezone versus IP location, language versus IP country, WebGL renderer versus claimed platform, WebRTC address versus connecting IP, and automation flags.
- An "inconsistent" result means two things disagree. It does not tell you which one is wrong, and patching one side usually moves the disagreement somewhere else.
- A "consistent" result means the pieces agree. It says nothing about whether your combination is rare or whether sites can link your visits. For that, see Browser Fingerprint Entropy and Anonymity Sets Explained.
- Different checkers pick different pairs and different strictness, so they disagree. See Why Fingerprint Test Tools Disagree About You.
What Pixelscan Is, and Who Pays for It
Pixelscan presents itself as an all-in-one checker covering IP, proxy or VPN status, fingerprint and bot signals. The free page is funded through partner placements. Its homepage carries an "Exclusive Partner Offers" section, a partner programme, and a utility that converts cookies into JSON, which is a tool for people who manage many accounts. In practice that puts it in the same family as Whoer: a free diagnostic that sits inside a commercial ecosystem aimed largely at multi-account and proxy users.
That is context, not an accusation. The underlying checks are ordinary and technically sound, and similar comparisons run in production bot-detection stacks. It does mean the tool is tuned for a particular audience, and its verdict wording reflects that audience's questions. This article names the tool in plain text only and does not link to it or to any of its partners, and it gives no steps for passing it. The aim is to explain what the verdict reads.
The Pairs a Consistency Verdict Compares
Without claiming knowledge of any private weighting, the comparisons a tool like this can sensibly make fall into a few families.
Claimed identity versus the engine actually running. The user-agent string says one browser and operating system. Other properties, such as which APIs exist, how the JavaScript engine behaves and what the platform string reports, reveal what is really executing. A user-agent announcing one platform over properties that belong to another is the classic mismatch. The site's user-agent spoofing guide walks through how that is caught.
Hardware story versus rendering reality. The WebGL renderer string names a GPU, and the screen size, core count and memory describe a device. These have to describe one plausible machine. Impossible Fingerprints: GPU/OS/Font Combinations That Flag You covers how an impossible combination, like a desktop GPU string on a phone-sized screen, stands out.
Timezone and language versus IP geolocation. The browser reports a timezone and language list. The server sees an IP address that geolocates somewhere. When these point to different countries, that is a mismatch, though a weak one on its own because travellers and expats are real. Timezone and Locale Leaks explains why this is one of the cheapest and most common checks.
WebRTC address versus the connecting IP. The WebRTC API can expose addresses independent of the page's main connection. If the address it reveals differs from the one the server sees, the network story does not hold together. See WebRTC Leak Protection for the mechanism.
Automation flags. Properties such as navigator.webdriver are defined to be true when a browser is under automated control. Their presence, or signs of tampering with them, feeds into whether a session looks driven by a script. The wider topic is covered in headless browser detection.
None of these checks alone proves anything. The verdict comes from how many disagree and how badly, which is exactly why the weighting matters and why it differs between tools.
Why "Inconsistent" Is Hard to Fix by Patching One Value
A consistency check compares at least two values, so editing one value rarely resolves a disagreement. It relocates it. Change the reported timezone to match the IP, and the system clock and locale-formatted dates may now disagree with it. Change the user-agent, and the feature set underneath no longer matches the claim. Mask the WebRTC address, and the absence of the usual candidate list can itself be unusual.
There is also a deeper point. Overriding a value in JavaScript often leaves traces of the override: a property whose descriptor looks wrong, a function whose string form is not native. Lie-detection approaches such as the one in CreepJS Explained look for exactly those traces, checking the same fact through several independent code paths. A tool that only compares two surface values and one that probes for tampering can therefore give different verdicts on the same browser, and neither is simply wrong.
Why Checkers Disagree With Each Other
Each vendor decides which pairs to compare, how strict a threshold to apply, and how to fold the results into a verdict. One tool may treat a timezone mismatch as a major failure, while another barely counts it. One may only look at the surface values, while another probes for tampering. A browser can therefore pass one checker and fail another without anything changing. This is the same effect described in Why Fingerprint Test Tools Disagree About You, and the same reason Whoer's percentage and a CreepJS trust score are not interchangeable. Read each as that tool's opinion about your setup, not a portable unit.
A Green Result Is Not Anonymity
This is the most useful point for an ordinary reader. Consistency means your signals agree. Anonymity means you are hard to single out. They are independent.
A completely stock browser on a normal home connection is perfectly consistent, and may still have a rare combination of fonts, screen size and hardware that makes it recognisable across sites. Conversely, a very common configuration can be anonymous within a large crowd while still failing a strict consistency test because of one stray mismatch. A green verdict tells you that nothing contradicted itself. It does not tell you how many other people look like you. The entropy article linked above explains how to read that second quantity.
A Neutral Second Opinion
If you want to see the underlying signals laid out individually rather than collapsed into a single verdict, BrowserInsight's fingerprint check and bot detection pages run a client-side consistency check, and the VPN and proxy check covers the network-side comparison a browser-only test cannot make. All fingerprint collection happens in your browser, and nothing is sent to a server. They share a detection-item contract, so a mismatch is named the same way on each. We make no claim of feature parity with any specific module of another tool; the point is simply to see which pair disagrees and why.
Frequently Asked Questions
What does an "inconsistent" verdict on Pixelscan mean?
It means at least one pair of signals contradicted each other, for example the timezone and the IP location, or the claimed platform and the rendering hardware. It does not identify which side is wrong, and it does not mean you are blocked anywhere. Look at which comparison failed and treat that as the lead.
Does a consistent result mean I am anonymous?
No. Consistency means your signals agree with each other. Anonymity depends on how many other browsers share your combination, which a consistency check does not measure.
Why do different checkers give different verdicts for the same browser?
Each one chooses its own comparisons, thresholds and weights, and none of these are standardised or, in most cases, published. The same browser can legitimately pass one tool and fail another.
Is Pixelscan the same as an official detection system?
No. It is a public checker with its own method. Real sites use their own stacks, which may compare similar pairs but with different rules, so a pass or fail on any public tool is not a prediction of how a particular site will treat you.
Recommended Reading
- Why Fingerprint Test Tools Disagree About You
- CreepJS Explained: How Fingerprint Lie-Detection Catches Spoofing
- What Whoer's Anonymity Score Actually Measures
- Timezone and Locale Leaks: When Your Browser Contradicts Your IP
- Impossible Fingerprints: GPU/OS/Font Combinations That Flag You
- WebRTC Leak Protection: A Must for VPN Users
- Browser Fingerprint Entropy and Anonymity Sets Explained
