Skip to content

BrowserScan, explained

BrowserScan gives your browser an authenticity percentage and lists exactly what it took points off for. That makes it one of the easier tests to read, as long as you know which deductions come from your connection rather than your browser.

A commercial site; its menu links to an anti-detect browser. Open BrowserScan

What is BrowserScan?

BrowserScan (browserscan.net) shows a single "Browser fingerprint authenticity" percentage, with each deduction listed underneath it, such as "-10%" for an IP that doesn't match. Below that is a detailed breakdown: IP and location, proxy and DNS-leak checks, WebRTC addresses, hardware hashes (canvas, WebGL, audio, client rects, WebGPU) and software values such as time zone, languages and HTTP headers.

It also has separate pages for bot detection, WebRTC leaks and kernel (engine) detection. Its menu links to an anti-detect browser product.

What BrowserScan checks

Bot control

Whether the browser appears to be driven by a program. It deducts points and says the environment "appears to be controlled by a robot".

IP and WebRTC

Whether the IP the page sees matches the address WebRTC reveals. A mismatch is read as a hidden real IP.

Time zone

Whether the browser's time zone matches the time zone of the IP.

Hardware hashes

Canvas, WebGL, audio, client rects and WebGPU hashes, plus the GPU vendor and renderer, checked for signs of tampering.

Software

Operating system, browser version, user agent from headers and from JavaScript, languages, and whether they agree.

How to read your BrowserScan result

The percentage
100% minus the listed deductions. Read the list: each line names its cause.
"IP addresses are different"
The page and WebRTC saw different addresses. On a dual-stack home line this can simply be IPv6 for the page and IPv4 for WebRTC.
"Different time zones"
Your browser's time zone doesn't match your IP. Expected with a VPN, a proxy in another country, or a persona set elsewhere.
"Controlled by a robot"
The page saw automation. This is the deduction that actually separates a script from a person.

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.

BrowserBrowserScan said
Everyday Chrome 153, by hand100%
Genuine Chrome 153, Playwright85% · Bot control -5% ("controlled by a robot") · IP addresses are different -10%

The everyday Chrome scored 100%. The genuine Chrome under Playwright scored 85%: it was called a robot, and it also lost 10% because the page saw its IPv6 address while WebRTC saw IPv4, on an ordinary home line with no proxy.

Results that show up on normal browsers

  • "IP addresses are different" on a normal dual-stack connection, where the page loads over IPv6 and WebRTC reports IPv4. In the same run BrowserScan also showed "Proxy: Yes" for a home line with no proxy.
  • "Different time zones" whenever you use a VPN or proxy in another country without changing the browser's time zone to match.

FAQ

How is the BrowserScan score calculated?

It starts at 100% and subtracts a listed amount for each problem it finds, such as 10% for an IP mismatch or 5% for signs of automation. The list under the score tells you exactly what was deducted.

Why does BrowserScan say my IP addresses are different?

The address the page saw differs from the one WebRTC revealed. That is how a leaking VPN looks, but it is also what a normal dual-stack connection looks like when the page uses IPv6 and WebRTC uses IPv4. See what a WebRTC leak is.

Does BrowserScan detect Playwright?

It can: in our test it flagged a genuine Chrome driven by Playwright as "controlled by a robot".

Is 100% on BrowserScan the goal?

It is a sign that nothing on this page looks off, which is good. But the score only covers what BrowserScan measures; other sites weigh other things, including how you behave.

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.

Run the audit Other test sites

Related reading

Q&AWhat is a WebRTC leak, and how do you test for one?A WebRTC leak is when a page learns your real IP through WebRTC, bypassing your VPN or proxy. How to test for one, what a normal result looks like, and how to fix it.Q&AWhat is a timezone / IP mismatch?When a browser's timezone, locale and language don't match the geolocation of its IP (often a proxy), the contradiction flags the session as suspicious.Test guidePixelscan, explainedPixelscan tells you whether your browser fingerprint is "consistent" or "inconsistent", with four cards for location, proxy, masking and bots. In our test a person's everyday Chrome got "inconsistent" and "Masking detected", so a red result on its own proves very little.Test guideIphey, explainedIphey gives your browser a one-word trust verdict and a score out of 100. It is quick and popular, but the verdict is easy to misread: in our test every browser we tried, including a person's everyday Chrome, was called "Unreliable".