BrowserLeaks, explained
BrowserLeaks isn't one test with a score. It is a toolbox of separate pages, each showing the raw values your browser reports about one thing: your IP, JavaScript, WebRTC, canvas, WebGL, fonts, TLS and more. That makes it the best place to check one specific value.
An independent collection of browser test pages. Open BrowserLeaks
What is BrowserLeaks?
BrowserLeaks (browserleaks.com) is a long-running collection of browser privacy tests. Each page focuses on one surface and shows you the values a website can read, usually with no verdict at all. That is its strength: it doesn't guess what a value means, so you can see exactly what your browser says.
Because there is no single score, the useful question is which page to open. The ones below cover most of what fingerprinting and bot detection look at.
What BrowserLeaks checks
IP Address
Your public IP, its location and network, and the HTTP headers your browser sends.
JavaScript
The navigator object in full, including navigator.webdriver, the user agent, Client Hints, languages, cores, memory and screen.
WebRTC Leak Test
The addresses WebRTC reveals, which shows whether a VPN or proxy is being bypassed.
Canvas and WebGL
Your canvas fingerprint, and your GPU vendor, renderer and WebGL parameters.
Fonts
Which fonts the browser exposes, a strong signal of operating system and installed software.
TLS Client Test
Your TLS handshake, the layer that reveals the real client before any page loads.
How to read your BrowserLeaks result
- navigator.webdriver
- On the JavaScript page.
truemeans the browser was started under automation. A browser driven by a person reportsfalse. - WebRTC addresses
- Compare them with your IP. A different public address means WebRTC is not going through your VPN or proxy. A
.localname is Chrome hiding your local address, which is fine. - Time zone vs IP
- The JavaScript page shows your time zone and the IP page shows your location. If they don't match, fix whichever is wrong.
What real browsers scored
Measured on 20 and 21 September 2026 on one Windows 11 PC (NVIDIA RTX 3070) on a home fibre connection in the Netherlands, with no proxy or VPN. Three browsers: a person's everyday Chrome 153 with an ad blocker, used by hand; the same genuine Chrome 153 driven by Playwright; and Clearcote 153 driven by Playwright with a fingerprint seed.
| Browser | BrowserLeaks said |
|---|---|
| Genuine Chrome 153, Playwright | JavaScript page: navigator.webdriver = true |
| Clearcote 153, Playwright + seed | JavaScript page: navigator.webdriver = false |
BrowserLeaks has no overall verdict, so the useful comparison is one value. Driven by Playwright, the genuine Chrome announced itself with navigator.webdriver = true; Clearcote reported false, the same as a browser used by hand.
Results that show up on normal browsers
- A WebRTC host address ending in
.local. That is mDNS protection hiding your LAN address. - An IPv4 WebRTC address next to an IPv6 page address. On a dual-stack connection that is normal, not a leak.
FAQ
Is BrowserLeaks safe to use?
It shows you what any website you visit could already read. The tests run in your browser and display the values back to you.
Which BrowserLeaks test should I run?
For a VPN or proxy: IP Address and WebRTC Leak Test. For automation: the JavaScript page, starting with navigator.webdriver. For fingerprinting: Canvas, WebGL and Fonts.
Why doesn't BrowserLeaks give me a score?
It is designed to show raw values rather than judge them. For a scored, explained check of the same surfaces, run the Clearcote audit.
What does navigator.webdriver true mean?
The browser was launched with automation enabled, which Playwright, Puppeteer and Selenium do by default. See why navigator.webdriver reveals automation.
Want every check explained?
The Clearcote audit runs 272 coherence checks on whatever browser opens it, with a plain-English explanation and a fix for each one. Free, no account.
Related reading