Browser Fingerprint Checker
See every signal your browser hands to the sites you visit — and which of those signals contradict each other. Free, no signup, results stay on this page.
- Runs entirely in your browser
- Results are not uploaded
- No signup
See what this browser gives away
The check reads the signals this browser hands to every site you open — screen, fonts, GPU, timezone, language and more — then looks for signals that contradict each other.
Runs entirely in this browser. Nothing is uploaded, nothing is stored, no signup.
Now give every account its own device.
A clean browser is still one browser. Sendwin runs each profile in isolation with its own fingerprint, cookies and proxy, so the accounts you work on never look like they came from the same machine.
- Isolated profiles, each with its own fingerprint and cookies
- A proxy per profile, with the timezone bound to the proxy country
- Windows, macOS and Linux — plus cloud sessions when you need them
The free plan includes 10 minutes of cloud browsing a day.
What a browser fingerprint actually is
A browser fingerprint is the set of details your browser gives to every site you open: user agent and Client Hints, screen and window size, timezone, language, installed fonts, GPU, audio stack, hardware counts and dozens of smaller flags. On their own, none of them identify you. Read together, they form a profile stable enough to recognize the same browser across sessions, without a single cookie being set.
What actually gets accounts flagged is not being unusual. It is being inconsistent. A site doesn't need to know how rare you are — it only needs two of your signals to disagree. A Windows user agent with macOS font metrics. A US exit IP with a Berlin clock. A GPU string that never ships with the screen resolution you report. Contradictions like these are cheap to detect and impossible to argue with, and they are what this checker looks for.
What each signal group reveals
The scan groups signals the way detection systems do. Identity covers your user agent, platform and Client Hints — what your browser claims to be. Hardware covers CPU cores, memory, screen size and device pixel ratio. Rendering covers canvas, WebGL and audio output, which shift with your GPU and drivers. Locale covers timezone, language and number formatting. Network covers WebRTC and the addresses it can expose. Any one group is weak by itself. Read together, they narrow a visitor down fast, which is why sites collect all of them on the first page load.
Why spoofing one value makes you easier to spot
Most privacy add-ons change a single value: they randomize the canvas hash, or hide the user agent, or switch off WebGL. The site still measures everything else, and now your signals no longer line up. Randomizing per call is detectable on its own — a canvas that returns a different hash twice in a row is not a real device. The same goes for timezone tricks that patch the JavaScript API while web workers keep reporting the true zone. A badly patched signal is louder than the original one you were trying to hide.
What a coherent identity looks like
A believable browser is boring. The user agent, Client Hints, platform and installed fonts all describe the same operating system. The GPU string is one that actually ships with that OS, and the WebGL limits match that GPU. The timezone matches the country the connection exits from, and the language settings agree with both. Values stay identical across reloads, inside iframes and inside web workers. Nothing here needs to be rare. It needs to hold together under repeat measurement, from every context a site is able to measure it from.
What you can actually do about it
If you browse normally, reduce what you hand over: keep your browser current, drop extensions that advertise fingerprint randomization, and leave your window at a normal size. If you run multiple accounts, patching values one at a time will not hold. Each account needs its own consistent environment instead. That is what Sendwin does at the engine level — every profile gets a full fingerprint that agrees with itself, its own proxy, and a timezone bound to that proxy's country, so the identity survives a second look instead of falling apart on the second signal.
How the check works
- 1
Run the scan
Open the page and the checker reads what any site could read: user agent and Client Hints, screen, hardware, fonts, canvas, WebGL, audio and locale. It takes a couple of seconds.
- 2
Read the result
You get one score out of 100, plus the two numbers behind it: how many signals contradict each other, and how many identifying values you hand over. All of it is computed from this browser alone.
- 3
Work through the conflicts
Every contradiction is listed with the two values that clash and why they clash. Fix the ones you control, then run the scan again to confirm the conflict is gone.
Check one signal at a time
When the full scan flags something, these go deeper on one group at a time and explain what the rows mean.
Browser fingerprint FAQ
Straight answers on what a fingerprint is, what you can change, and what this check can and cannot see.
It's the combination of details your browser exposes to every site you visit — user agent, screen size, timezone, language, fonts, GPU, audio stack, hardware counts and more. No single value identifies you, but the combination is stable enough that a site can recognize the same browser again without storing a cookie.
You can change parts of it, but hiding it entirely isn't realistic — a browser that refuses to answer basic questions stands out immediately. Changing one value at a time usually makes things worse, because the value you patched no longer agrees with the ones you didn't. What works is a browser that presents a complete, self-consistent identity, which is what an anti-detect browser like Sendwin gives each profile.
No. Incognito clears cookies and history for the session; it doesn't change your screen size, fonts, GPU, timezone or any other signal, so your fingerprint is the same before and after. A VPN changes the IP address sites see, but everything the browser reports stays put — which is how you end up with a foreign IP and a local clock, one of the easiest mismatches to catch.
No. Cookies and fingerprints are separate identifiers. Clearing cookies removes what a site stored on your machine; fingerprinting reads what your machine reports, so the same profile comes straight back on your next visit. That's exactly why sites use it — it survives clearing cookies, private windows and switching accounts.
It reads the same APIs a site would read, so what you see is what a site sees from this browser, right now. It can't see what a site does with those values afterwards, and it can't check signals that only appear on a real login attempt, such as behavioral timing. Treat it as an accurate reading of your exposure, not a pass or fail from any particular platform.
No. The scan runs in your browser and the results are not uploaded — they exist only in the page in front of you, and reloading clears them. There's no account to create, and nothing to delete afterwards.
Aim for coherence first. A high score with no contradictions is a normal browser and generally fine. A lower score driven by conflicting values is the pattern that gets attention, because it reads as a browser that has been tampered with. If you're running one account per browser, fix the conflicts and stop there. If you're running many, give each one its own consistent environment.
Because a fingerprint describes the browser, not just the machine. Chrome, Firefox and Safari ship different font lists, different WebGL implementations and different audio pipelines, so each produces its own set of values on identical hardware. Profiles inside the same browser can differ too, once extensions or settings change what gets reported.
Still have questions? Talk to us →
How to read the score
One caveat worth repeating: this tool measures what this browser exposes right now and whether those signals agree with each other. It is not a ranking against a database of other visitors — we don't keep one. Read the score as a checklist of what you're handing over and where it contradicts itself, not as a uniqueness percentile.
Fix the conflicts once, per profile.
Sendwin builds each profile as one coherent device — fingerprint, fonts, GPU and a timezone bound to its proxy country. Free for 30 days on Windows, macOS and Linux.
30-day free trial · $0 today · cancel anytime — your profiles stay on your machine