What Is Browser Fingerprinting?
When you visit a website, your browser sends far more information than just your IP address. The combination of your browser version, operating system, screen resolution, installed fonts, timezone, language, graphics hardware, and dozens of other attributes creates a "fingerprint" — a profile that's often unique enough to identify you across sessions, even after clearing cookies.
Unlike cookies, fingerprints don't require anything to be stored on your device. The tracking happens server-side, making it impossible to "delete" and difficult to detect.
The Data Points That Make Up Your Fingerprint
- User-Agent string — browser name, version, and OS
- Accept-Language header — your preferred language and locale
- IP address — your approximate location (though this changes with VPNs)
- Screen resolution and color depth
- Browser window inner dimensions
- Timezone and whether DST is active
- List of supported MIME types
- Installed plugins (largely deprecated in modern browsers)
- Do Not Track header setting
- Touch event support
- Cookie and localStorage availability
- Canvas fingerprint — render a specific canvas element and hash the pixel output. Different GPU drivers produce subtly different renders, creating a hardware-level identifier that persists across browsers on the same machine.
- WebGL fingerprint — similar to canvas but using 3D rendering
- AudioContext fingerprint — process an audio signal through the browser's audio pipeline and hash the output
- Font enumeration — measure the dimensions of text rendered in different fonts to detect which fonts are installed
How Unique Is Your Fingerprint?
Research by the Electronic Frontier Foundation's Panopticlick project found that 83.6% of browsers had a unique fingerprint. Adding canvas and WebGL fingerprinting pushes that number higher. A unique fingerprint means a site can identify you with high confidence even without any cookies.
The challenge is that making your browser look "normal" is harder than it sounds. If you set your browser to report a common screen resolution but have unusual fonts, or if you use an old user-agent string but have modern WebGL capabilities, the inconsistencies themselves become identifying.
What NoxaKit's Browser Info Tool Shows
NoxaKit's Browser Info tool displays everything your browser exposes through standard APIs — user-agent, timezone, screen size, color depth, touch support, language, and more. This is the same data collection that fingerprinting scripts use. Checking your own profile helps you understand what's visible.
The User-Agent Parser breaks down your UA string into browser name, version, engine, and OS — useful for debugging cross-browser issues or verifying that a spoofed UA is formatted correctly.
What You Can Do
**Use Firefox with privacy hardening.** Firefox's Enhanced Tracking Protection blocks known fingerprinting scripts, and Mozilla actively works to reduce fingerprinting surface area. Chrome's fingerprinting mitigations are weaker.
**Tor Browser provides the strongest fingerprinting resistance** by making all users look identical — same window size, same fonts, same canvas output. The tradeoff is slow speeds and broken websites.
**Brave** ships with fingerprinting randomization — each session reports slightly different canvas and audio values, making cross-session tracking harder without the compatibility issues of Tor.
- Clearing cookies (fingerprint doesn't use cookies)
- Incognito/private mode (same browser APIs, same fingerprint)
- VPN alone (changes IP, not fingerprint)
- Most "fingerprint blockers" (easy to detect and work around)
The Honest Picture
Browser fingerprinting is used by ad networks, fraud detection systems, and analytics providers. It's also used legitimately — banks use it as a secondary factor to detect account takeover. Complete fingerprint resistance requires trade-offs in usability. Understanding what's collected is the first step to making an informed decision about which trade-offs make sense for you.