Pixelscan Results Explained
Pixelscan answers three questions at once: is this connection a proxy, does the browser fingerprint look masked, and do all the browser’s claims agree with each other and with the IP. People usually arrive here after a red result. Pixelscan documents little of its method, so this guide uses what it does publish, its own FAQ text, its changelog and the structure of its page code read on October 30, 2026, to explain each result and which ones a real website would care about.
Short answer
- The proxy result is about the connection. The masking and consistency results are about the browser. Fix them separately.
- Pixelscan’s code models consistency as one of three states: consistent, unsure or inconsistent. Unsure is not a failure.
- Pixelscan’s own changelog records fixes for false masking alerts on iOS, Android, Linux and Safari. Retest before you rebuild a profile.
- For proxied browsing, the reds that matter most are location ones: IP country against time zone and language, and WebRTC exposing another address.
The proxy result
The proxy line reports whether Pixelscan believes the connection passes through a proxy or VPN. Pixelscan does not publish how it decides, and its changelog mentions several updates to the proxy detection mechanism without describing them. Checkers of this kind usually combine IP database labels (hosting, VPN, proxy) with comparisons between the IP and what the browser reports.
Pixelscan also runs a separate proxy checker for testing a proxy you enter, plus single-purpose pages for WebRTC, DNS, VPN detection, location and IP blacklists. These are different tools from the main scan. If the main scan says proxy and the dedicated checker does not, they are measuring different things.
A proxy label on its own is common and not alarming. Many websites see proxied, VPN and corporate traffic every day. The label matters when it comes with a mismatch that makes the session look inconsistent.
The fingerprint and masking result
Pixelscan’s FAQ says it runs fingerprint tests in the browser to measure uniqueness across signals such as WebGL, canvas, audio, fonts, media devices and system settings, and shows which values contribute most to how identifiable you are. The masking result is separate: it looks for traces that the fingerprint has been altered, for example noise added to canvas output.
Masking alerts are the result most worth retesting. Pixelscan’s changelog lists fixes for false masking detection on iOS, on mobile devices in general, on Linux, on Safari for macOS, on Android browsers and on slow connections, and fixes for false automation alerts on Edge, Safari and manually controlled browsers. A checker that has corrected false positives this often can still produce them. Run the scan twice, in a second browser if possible, before concluding anything.
Consistency: do the claims agree
| Mismatch | Typical cause | Fix |
|---|---|---|
| IP country against time zone | Proxy in one country, device clock in another | Set the profile time zone to the exit location |
| IP country against language | Browser language left at your home setting | Match the profile language to the exit |
| WebRTC address against browsing IP | WebRTC reaching out around the proxy | Limit WebRTC in the profile |
| User agent against platform or fonts | User agent changed, everything else left alone | Change the whole profile or nothing |
| Screen, GPU and cores against device | Phone user agent on desktop hardware | Use a profile that matches the real device class |
Consistency is the core idea. A browser makes many claims, and real devices produce claims that fit together. In Pixelscan’s page code the consistency value is one of three states, and its changelog notes that audio fingerprint checks were added to the consistency logic. Typical disagreements:
Fixing a red result, in order
- Confirm the IP. Open What is my IP in the same profile and note the address, provider and time zone. If the address is not the proxy’s, fix the proxy setup first.
- Fix WebRTC. Our WebRTC leak test lists the candidates your browser exposes. Under RFC 8828, browsers can restrict WebRTC to the default route or force it through the proxy; choose the mode that exposes only the proxy address.
- Align time zone and language with the exit location.
- Remove partial spoofing. Extensions that alter one value, such as canvas or user agent, create the very mismatches the scan looks for.
- Retest twice. Keep the same IP for both runs; on a rotating line, pause rotation while testing.
If the masking alert persists on a stock browser with no extensions, consider the false-positive history above before changing anything else.
Which results matter on real sites
The W3C’s guidance on browser fingerprinting notes that active fingerprinting, done by scripts in the page, is potentially detectable, and that removing fingerprinting entirely is implausible. Real defenses therefore look for contradictions and behavior, not for a perfectly anonymous browser. Location mismatches and WebRTC exposure are visible to any page, so they matter everywhere. A high uniqueness reading matters less on its own: real browsers differ from each other too, and a site cannot refuse every visitor who is distinctive.
Websites also use signals no page checker shows. Cloudflare lets its Bot Management customers write rules on JA3 and JA4 TLS fingerprints, which describe how the client opens a secure connection. You can see your own with our JA4 fingerprint checker.
On the connection side, Coronium mobile proxies give a carrier address from a physical device with its own SIM, rented to one customer, so the IP is not a hosting range. The browser-side results still depend on your profile. Our antidetect browser guide covers profile setup in more depth.
Sources and review scope
Sources reviewed October 30, 2026. Each checker was reviewed on October 30, 2026 from its own documentation, its published page scripts or an archived copy of its page, as the article states. Checkers change without notice, and a checker verdict is not a website’s decision. We do not see any site’s private risk rules.
Frequently asked questions
Read another checker
How each public checker reaches its verdict, and which of its findings a real site can act on.
Related workflows
See which signals a page can read from your browser.
Profile tools compared for consistency and control.
A checker with a single Trustworthy or Unreliable verdict.
Raw values without a verdict, page by page.
Separate the exit IP, GeoIP data and browser location.
ICE candidates and public-address exposure.
The full set of error and checker guides.
Where to get a dedicated line
A Coronium mobile proxy is one physical device with its own SIM, rented to one customer. It connects over HTTP or SOCKS5, the IP changes by dashboard button, API link or timer, and data is not metered on dedicated lines. Brazil lines are the exception: 20 GB of data a month and a new IP on request only, with no timer. Stock and prices differ by country and carrier.