Pixelscan
Consistency check: does the browser's story match the connection's?
Pixelscan runs a fingerprint scan and an IP lookup in the same visit, then looks for the places where the two disagree — a Spanish address under a browser set to Moscow time, a desktop user agent on a touch-only device. It ends with a verdict rather than a table of values, which is what makes it the first stop for anyone testing an anti-detect profile.
What it checks
- IP address, ASN, and whether it belongs to a hosting provider
- Canvas, WebGL and font fingerprints, with their uniqueness
- Timezone, language and locale against the country of the IP
- Automation traces: WebDriver, headless markers, injected scripts
How to read the result
A green result means nothing contradicted anything else — not that you are anonymous. The useful part is the list of individual checks underneath the verdict: one red line tells you which part of the profile leaks.
What it does not prove
A clean Pixelscan result is a floor, not a ceiling. Its checks are published, so anti-detect builds are tuned against exactly those; the invariants a payment gate looks at — whether canvas noise moved pixels that physics says cannot move — are not on its list.
These tools are run by their own operators, not by us. Opening one sends your IP address and browser details to that site.
