Browser fingerprint test
Runs in your browser · freeEverything your browser reveals to websites, and whether those values agree with each other.
| User agent OS vs navigator.platform | … |
| User agent OS vs client hints | … |
| Page vs web worker | … |
| Language vs timezone | … |
| Screen vs available area | … |
| OS vs graphics renderer | … |
| WebRTC IP exposure | … |
Browser and system
| User agent | … |
| Client hints | … |
| Browser brands | … |
| navigator.platform | … |
| CPU cores | … |
| Device memory | … |
| Screen | … |
| Pixel ratio · colour depth | … |
| Touch points | … |
| Cookies · Do Not Track | … |
Location and language
| Timezone | … |
| UTC offset | … |
| Languages | … |
| Locale (Intl) | … |
| Number format | … |
Graphics and audio
| WebGL vendor | … |
| WebGL renderer | … |
| WebGL parameters hash | … |
| Canvas hash | … |
| Audio hash | … |
WebRTC
Full WebRTC test| WebRTC | … |
| Public IP via WebRTC | … |
| Local IP via WebRTC | … |
Detected fonts
of 34 testedNothing on this page is sent to NexLogin.
What this test checks
Websites can read dozens of values from your browser without asking permission. On their own most are common, but combined they often identify one browser among millions. This test shows the main ones, in the same way a tracking script would read them.
| Signal | What it reveals |
|---|---|
| User agent and client hints | Browser, version and operating system |
| Screen and hardware | Display size, pixel ratio, CPU cores and memory |
| Timezone and languages | Where you probably are, which should match your IP address |
| Canvas | Tiny differences in how your GPU, drivers and fonts draw text and shapes |
| WebGL | Your graphics card model and its capabilities |
| Audio | How your audio stack processes a test signal |
| Fonts | Installed fonts, which differ by operating system and software |
| WebRTC | Your public IP address and sometimes your local network address, even behind some proxies |
How to read the consistency checks
Fingerprint protection that changes values at random often breaks the links between them. A Windows user agent next to a Mac platform value, or a page and a web worker that report different values, are easy for a site to spot. Good protection keeps every value consistent with one believable device. That is the approach NexLogin takes for each browser profile.
Fingerprint test FAQ
What is a browser fingerprint?
A browser fingerprint is the set of values your browser reveals to every website: user agent, screen, timezone, fonts, graphics card, and how it draws canvas and audio. Together they are often unique enough to recognise you without cookies. See browser fingerprinting explained.
Does this test send my data anywhere?
No. Every check runs in your browser and the results stay on this page. The only outside request is the WebRTC check, which asks a public STUN server for your public IP address, exactly as a video call would.
What do the consistency checks mean?
They compare values that should agree, such as the operating system in your user agent and in navigator.platform, or the values seen by the page and by a web worker. A mismatch is a common sign of a spoofing extension, and sites look for it.
Why does my fingerprint ID change?
It changes when anything in it changes: a browser update, a new monitor, an installed font, or a privacy extension that adds noise. A stable ID across visits is what makes fingerprinting useful for tracking.
How do I stop sites linking my accounts through my fingerprint?
Give each account its own browser profile with a separate, consistent fingerprint, proxy and storage. That is what an antidetect browser such as NexLogin does.
Give every account its own fingerprint
NexLogin runs each account in an isolated browser profile with a consistent fingerprint, its own proxy and its own cookies.