📘 Checklist: what to fix now, what can wait →

Browser fingerprint check

Open this page inside each browser profile (AdsPower, Multilogin, GoLogin and similar). We list the fingerprint, flag values that contradict each other and give an ID so you can tell whether two profiles are duplicates.

Fingerprint ID ?····-····
ResultChecking…

Open this page in each profile and compare IDs. The same ID means the two profiles share the same fingerprint.

📋 Test history on this device 0

Saved only in this browser on this device. Nothing is uploaded.

Fingerprint details

Frequently asked questions

What is an antidetect (fingerprint) browser?

An antidetect browser creates separate browser profiles, each with its own cookies, proxy and fingerprint values, so that several accounts can be run from one computer. Agencies and teams that manage stores or ad accounts for different clients use them. Each platform has its own rules on how many accounts one person or business may hold — check and follow them; a tool like this only helps you see what your browser reveals.

Why are contradictions worse than a common fingerprint?

Millions of people share common devices, so an ordinary fingerprint is not suspicious in itself. A fingerprint that is impossible in the real world is: for example a Windows user agent with an Apple GPU, a Chrome version that differs between the user agent and Client Hints, or Windows with only macOS fonts. These happen when a few values are changed but related values are not, and they are easy for risk systems to spot.

What does the fingerprint ID mean and how do I use it?

The ID is a short hash of the stable parts of the fingerprint: canvas, WebGL, audio, fonts, screen, hardware, time zone, languages and user agent. Open this page in every profile and write the IDs down. If two profiles show the same ID, they look like the same device to a website. The ID is calculated in your browser and is not stored by us.

What are canvas, WebGL and audio fingerprints?

Canvas fingerprinting draws text and shapes and reads back the pixels, which differ slightly by GPU, driver and fonts. WebGL can also report the graphics card name through the WEBGL_debug_renderer_info extension defined by Khronos. Audio fingerprinting processes a test signal and reads back tiny numeric differences. The W3C guidance on fingerprinting describes these as typical high-entropy sources. If a value changes every time it is read, random noise has been added — some browsers do this for privacy, but it can also be noticed.

References