See exactly what your browser reveals

How to read what the checker just told you

The values above are a list, not a verdict. What matters is not whether any single one is unusual, but whether they agree with each other, because detection is mostly contradiction-finding. A site that wants to know whether two accounts are the same person rarely relies on one clever measurement; it collects a few dozen ordinary ones and looks for the combination, and for the places where the combination does not make sense as a real machine.

User agent and client hints

The user agent is the browser announcing itself, and it is the easiest thing in the world to change -- which is exactly why it is no longer trusted on its own. Modern Chrome also exposes client hints, a structured version of the same claims: platform, architecture, full browser version, whether the device is mobile. A spoof that edits the user-agent string and leaves the client hints reporting the real platform has produced a contradiction on the very first check a site runs. When you view this page inside a profile, the two should tell the same story.

WebGL vendor and renderer

These name your graphics stack -- typically a vendor and a specific GPU model, drawn from the driver. They are among the highest-signal values on the page because they are stable, granular and hard to fake convincingly. The failure mode to look for is a GPU that does not belong with the rest of the identity: a discrete workstation card on a profile claiming to be a budget laptop, or a renderer string naming a software rasteriser, which almost never appears on a real desktop and marks the session as something running in a container or a virtual machine.

Canvas, audio and font hashes

All three work the same way: ask the machine to render something -- a line of text to a canvas, a tone through the audio pipeline, a string in a list of typefaces -- and hash the result. Tiny differences in GPU, driver, operating system version and installed fonts produce a stable value that is the same on every visit and different between devices. Two things can go wrong here. A hash identical to millions of other visitors says a tool is reporting a stock value rather than a device. A hash that changes on every page load says it is adding random noise, which is just as distinctive, because real hardware does not produce a different answer each time you ask. What you want is a value that is stable for this profile and different from your other profiles.

Fonts

The list of installed typefaces is a surprisingly strong identifier, because it accumulates the software history of a machine -- an office suite, a design tool, a language pack each leave fonts behind. Two checks are worth making. Does the list fit the operating system being claimed, since a Windows profile listing macOS system fonts is a straightforward contradiction. And is the list plausibly sized: a machine reporting only the handful of fonts in a bare install looks like a fresh virtual machine, which is not what most real users are browsing from.

Timezone, language and geolocation

This is where most setups actually fail, and it has nothing to do with the browser engine. If the request arrives from an IP in Germany while the browser reports a New York timezone and sends an Accept-Language header of en-US, no fingerprint work anywhere else on the page rescues it. The timezone should follow the proxy exit, the language should be plausible for that location, and the geolocation permission, if granted, should not place you on another continent. Check these three together, and check them again after changing a proxy.

The WebRTC leak test

WebRTC exists for peer-to-peer audio and video, and to make a direct connection it asks the operating system for your real network addresses. That request goes around a proxy, which is why a browser can be perfectly configured on every other axis and still hand a site the home IP address of the person using it -- the single most damaging leak in this whole area, because it links every account on that connection at once. The test above should show the proxy exit address and nothing that looks like your own network. If you see a second, unexpected address, stop and fix that before anything else on this page.

Hardware, screen and platform

Processor core count, device memory, screen resolution, colour depth and the available screen area net of the taskbar are individually weak and collectively useful. They also constrain each other in ways that are easy to get wrong: a device claiming two cores and 64 GB of memory is not a configuration anyone ships, and a window whose reported inner dimensions exceed the screen it says it is on is not physically possible. The values should describe a computer that could be bought.

What a good result actually looks like

Not maximum uniqueness. A believable, internally consistent machine whose values stay the same the next time you open the profile, and differ from your other profiles. Open this page in two profiles side by side: the hashes should differ, the story each one tells should be coherent, and neither should change when you close and reopen it a week later. That combination -- distinct between profiles, stable within one -- is the whole objective, and it is what Dual Login applies in the browser core rather than by injecting JavaScript, which is why the values also hold inside web workers where injected spoofing frequently stops applying.