Websites read dozens of small details from your browser and combine them into an ID that follows you without cookies. This scan shows each signal and its value, so you can see what an antidetect profile has to get right.
Your fingerprint ID
Scanning your browser…
Everything is computed in your browser. Nothing on this page is sent to XProxy or anywhere else.
Scan again and the ID should stay the same. It is a hash of the stable signals below (canvas, WebGL, audio, fonts, navigator, screen, timezone, plugins).
Canvas
What sites use it for: Your browser draws a hidden image. Small differences in your GPU, drivers and fonts change a few pixels, and sites hash the image into a stable ID. Antidetect browsers add noise or swap the result; an image that changes on every read is a giveaway too.
WebGL (graphics card)
What sites use it for: Reports your graphics card, driver and limits. Anti-fraud systems check that the GPU fits the operating system in your User-Agent, and software renderers such as SwiftShader or llvmpipe point to a headless bot or a server.
AudioContext
What sites use it for: Renders a short sound in memory without playing it. Tiny differences in the audio stack give a stable number that works as one more device ID.
Fonts
What sites use it for: Windows, macOS and Linux ship different fonts, so the list of installed fonts reveals the real operating system. Sites find them by measuring how wide a test string is in each font.
Browser & navigator
What sites use it for: User-Agent, platform, languages, CPU cores and memory. Sites compare these with each other and with the country of your IP address; any contradiction raises your risk score.
Client hints (userAgentData)
What sites use it for: Chromium sends brand, version, platform and architecture as structured data. It has to agree with the User-Agent string; a User-Agent that was edited without updating the hints is a classic antidetect mistake.
Screen & window
What sites use it for: Resolution, pixel ratio, colour depth and window size. Rare or impossible combinations narrow you down and expose emulated devices.
Timezone & locale
What sites use it for: Your timezone and date format. Sites compare the timezone with the location of your IP address; a mismatch is one of the most common proxy tells.
Plugins & MIME types
What sites use it for: A normal desktop Chrome lists its built-in PDF viewer. An empty list is typical for headless and automated browsers.
Permissions
What sites use it for: The current state of a few permissions, read without asking for any of them. Headless Chrome is known to answer inconsistently between Notification.permission and the Permissions API.
Media devices
What sites use it for: How many microphones, speakers and cameras the browser reports. Real desktops almost always have at least one speaker; servers and virtual machines often report none.
What a browser fingerprint is
A fingerprint is not one value. A website reads many properties (graphics card, fonts, screen, language, timezone and more), combines them and recognises the same combination on your next visit, even after you clear cookies or switch IP address. Each signal above is only a clue; together they are usually specific enough to tell one browser from another.
Why it matters for proxy and antidetect users
A proxy changes your IP address but not your browser. If one fingerprint shows up on fifty accounts, those accounts are linked. If the fingerprint contradicts the IP, for example a Windows User-Agent on an Apple GPU or a US IP with a Vietnamese timezone, the account is flagged. Antidetect browsers such as AdsPower, GoLogin, Multilogin and Dolphin{anty} create a separate, self-consistent fingerprint for every profile.
How to use this result
Open this page inside one profile and note the ID. Open it in a second profile: the IDs should differ. Reload the first one: its ID should stay the same. Then run the Antidetect Health Check to see whether the signals agree with each other and with your proxy.
No. Every signal is read and hashed inside your browser and stays on this page. The scan makes no network request with your data, and closing the tab discards it.
Why does my fingerprint ID change when I scan again?
It should not. If canvas or audio change on every scan, your browser or antidetect profile is adding random noise, and some sites treat that as a sign of spoofing. Use a fixed noise seed per profile so the same profile always shows the same values.
Is a unique fingerprint good or bad?
Neither on its own. What raises risk is a combination that is impossible for a real device (a Windows User-Agent with an Apple GPU) or the same fingerprint on many accounts. Each account should have its own consistent profile.
Can a proxy change my browser fingerprint?
No. A proxy changes your IP address and the network-level (TCP/IP) fingerprint, not what your browser reports. For the browser side you need an antidetect browser such as AdsPower, GoLogin or Multilogin, set up so the profile matches the proxy.
The network side of the fingerprint
The browser is only half of what a site sees. XProxy mobile proxies give you real carrier IPs and a TCP/IP fingerprint that matches the device you choose, so your antidetect profile and your connection tell the same story.
