Privacy tool
Browser Fingerprint Test
Check which browser and device signals websites may use to recognise you without cookies. The test runs in your browser and shows an exposure score plus the individual signals detected.
What browser fingerprinting can reveal
Websites can combine details such as your browser version, language, timezone, screen size, device memory, CPU hints, plugins, canvas rendering, WebGL renderer, and installed fonts. One signal alone may be harmless, but the combination can make your browser easier to recognise across visits. This test also checks one signal that comes from your network connection rather than your browser: the TLS handshake your device performs when it connects to a server, which can vary by operating system, VPN client, and network stack even when your browser stays the same.
How to reduce your fingerprint
- Use a privacy-focused browser or a separate privacy browser profile.
- Block third-party cookies and known trackers.
- Consider browser settings or extensions that restrict canvas and WebGL readouts.
- Keep browser language, timezone, and VPN location consistent when privacy matters.
- Retest after changing browser settings, VPN servers, or privacy extensions.
Useful next checks
Browser fingerprinting is only one privacy signal. You should also check for WebRTC leaks, DNS leaks, and whether your VPN is working as expected.
Frequently asked questions
What is browser fingerprinting?
Browser fingerprinting is a tracking method that uses details about your browser, device, screen, timezone, graphics rendering, and settings to recognise you without relying only on cookies.
Is a browser fingerprint the same as cookies?
No. Cookies are stored data that can usually be cleared or blocked. Fingerprints are inferred from the way your browser and device behave, so they are harder to reset.
Can I completely stop fingerprinting?
It is difficult to stop all fingerprinting while using normal websites. You can reduce exposure with privacy-focused browsers, stricter tracking protection, script blocking, and consistent privacy settings.
Why does this tool show an exposure score?
A true uniqueness score requires a large comparison dataset. This tool instead shows which fingerprinting signals your browser exposes locally and how risky those signals are.
Does the TLS signal here match tools that use JA3 fingerprinting?
Not exactly. This signal is built from real TLS handshake data our server can see: the cipher suite and extensions your connection offered. The specific JA3 hash format some security tools use needs an enterprise-tier feature we do not run, so we show a genuine TLS-based signal rather than claim a JA3 match.
How does the font signature work if browsers do not list installed fonts?
Browsers do not hand over a list of installed fonts directly, so this test measures rendered text width for a set of common fonts against generic fallbacks. If the width differs, that font is very likely installed. It is an inference, not a direct read, and modern browsers increasingly limit how much this can reveal.