What is a browser fingerprint
A browser fingerprint is the set of parameters a website reads without cookies: User-Agent, screen, languages, timezone, graphics card via WebGL, Canvas and Audio hashes, fonts and CPU core count. Each one is ordinary on its own, but together they are almost unique and identify you even in incognito mode or after clearing cookies.
Anti-fraud systems at ad networks, marketplaces and crypto projects compare these fingerprints across accounts. Two accounts with the same Canvas and WebGL, or with different IPs but identical hardware, are treated as one owner and banned as a chain.
Which mismatches expose multi-accounting most often
The browser timezone does not match the IP timezone: the proxy is in Germany while the clock shows New York. This is the first thing Iphey and Pixelscan check.
WebRTC leaks: behind a proxy a site sees one address, while WebRTC reveals your real one. User-Agent switcher extensions break consistency: the User-Agent says Windows while the platform and fonts say macOS. The navigator.webdriver flag and software WebGL rendering (SwiftShader, llvmpipe) reveal automation and virtual machines.
How this test differs from Iphey, Pixelscan and BrowserLeaks
Iphey and Pixelscan give a single verdict, BrowserLeaks shows raw data for each technology separately. This test combines both: it puts the key parameters in one table and explains in plain words what is wrong and how to fix it. Nothing is stored: everything runs in your browser, and only the IP lookup goes to our server.
How to get a clean fingerprint for every account
Clearing cookies and incognito mode do not change your fingerprint. A VPN changes only the IP. Spoofing the User-Agent with an extension makes the fingerprint even more noticeable. The reliable way is an antidetect browser: every profile gets its own consistent set of real-device parameters, its own proxy and its own cookies, so accounts cannot be linked.