Testing guide
Browser fingerprint checkers compared
Many free sites test your browser fingerprint. They check different things and score them in different ways. This guide shows what each one is good for, and how to read the results.
Direct answer
No single checker is the best. Use one that explains each result, then confirm a warning on a second one. BrowserLeaks shows raw values. CreepJS finds browser functions that a script changed. AmIUnique and Cover Your Tracks measure how unique you are. Pixelscan, BrowserScan, Iphey and Whoer give a quick verdict, but some of their warnings also appear for stock browsers. The free AliasMode test fails only values that a stock browser never shows, and it explains each fix.
The checkers at a glance
| Checker | What it checks | Verdict style | Caveat |
|---|---|---|---|
| Pixelscan | Fingerprint, proxy, IP and DNS leaks. Separate pages for bot, WebRTC and VPN checks | Short labels, such as “Proxy detected” and “Timezone spoofed” | In our October 2026 benchmark, it said “Timezone spoofed” for every browser on a proxy, stock Chrome included, even when the time zone matched the proxy |
| BrowserScan | IP, WebRTC, location, canvas, WebGL, audio, screen. Separate pages for TLS and HTTP/2, bots, time zone, client hints, and engine against user agent | One “fingerprint authenticity” percentage | The percentage covers its own checks only. Open the detail pages to see the reasons |
| CreepJS | Browser functions that a script changed (“lies”), headless and stealth signs, canvas, WebGL, audio, fonts, screen and more | A fingerprint ID, a list of lies, and headless and stealth percentages | Dense, and made for research. Use only abrahamjuliot.github.io/creepjs. The author says copies on other domains are not official |
| BrowserLeaks | Separate pages for IP, JavaScript values, WebRTC, canvas, WebGL, fonts, TLS (JA3 and JA4), HTTP/2, DNS and client hints | Raw values, with no overall score | You compare the values yourself |
| Iphey | Fingerprint, IP, proxy or VPN, bot signs, DNS leaks and IP blacklists | One overall verdict with a trust score | It can flag a returning browser whose screen size or graphics card changed since the last visit. Clearing the site’s data resets this |
| Whoer | IP, provider, DNS and WebRTC leaks, time zone and language against the IP country, and a list of browser values | A leaks score | Most checks are about the IP and leaks, not the fingerprint |
| AmIUnique | Headers, plugins, platform, time zone, screen, canvas, WebGL, fonts, ad blocker and more | How many observed browsers share your fingerprint, and the share for each value | It stores your fingerprint and sets a cookie for four months. Unique does not mean flagged |
| Cover Your Tracks (EFF) | Tracker blocking, and how unique your fingerprint is among recent visitors | A tracker protection level and a uniqueness score | Made for tracking protection, not for proxy or account setups |
| Fingerprint.com demo | A visitor ID from more than 100 signals, plus bot and VPN signals | Your visitor ID, visit history and a confidence score | A product demo. The site says the ID stays the same in incognito mode or on a VPN |
| AliasMode test | IP, WebRTC, DNS, TLS and HTTP/2, time zone, language, user agent, client hints, engine version, automation, changed functions, canvas, WebGL and audio noise, fonts, screen | Pass, warning or fail for each check, with the fix | Warnings mark things that normal setups also cause. They are not failures |
How to read the results
Consistency beats uniqueness. Almost every browser is unique when many values are combined. So a “unique” result alone tells you little.
Sites care more about values that contradict each other. Examples are a Windows user agent with Mac fonts, a time zone far from the IP, or a browser function that a script replaced. They also care when two accounts share one fingerprint.
One checker’s warning is not proof. Each site reads different values and uses its own rules. Some warnings appear for every visitor on a proxy.
- Read the reason, not the score. A score hides which value caused it.
- Run a stock browser on the same network as a control. If it gets the same warning, the warning is not about your setup.
- Confirm a warning on a second checker before you change anything.
- Fix contradictions first: time zone and language against the IP, the WebRTC address, and the user agent against the engine.
- Test the same profile again on a later day. Values that change between visits can also stand out.
Why we built our own test
We ran stock browsers and many antidetect browsers through public checkers. Some warnings appeared for every browser, stock ones too. On 2026-11-02, Pixelscan showed “Timezone spoofed” for stock Chrome 156, whose time zone matched the proxy location. A warning that every browser gets tells you nothing.
So the AliasMode test fails a check only for a value that a stock browser never shows. Stock Chrome, Edge and Firefox on Windows, macOS and Linux pass it, and we check this every week. Things that normal setups cause are warnings. Each result says what the test found and how to fix it.
It still finds real problems. In our test on 2026-11-03 inside other antidetect browsers, it found old engine versions, canvas, WebGL or audio noise that a site can detect, and a foreign token in one user agent.
Shared results keep the verdicts only, with no addresses, for 30 days. Nothing else is stored.
Frequently asked questions
What is the best browser fingerprint test?
No single checker is the best. For an explained verdict, use a test that fails only real contradictions, such as the free AliasMode test. For raw values, use BrowserLeaks. To find changed browser functions, use CreepJS.
Why do two fingerprint checkers give different results?
Each checker reads different values and scores them its own way. Some flag every visitor on a proxy. Others measure how unique you are, not whether your values agree. Compare the reasons, not the scores.
Is a unique fingerprint bad?
Not by itself. Most browsers are unique. Sites care more about values that contradict each other, and about accounts that share one fingerprint.
Should I trust a “Timezone spoofed” warning?
Check it first. Compare your browser time zone with your IP location. If both are in the same zone, sites that compare the two see no mismatch.