Current with no public leak
The browser is current, important policy tests pass and WebRTC does not reveal a different public address.
Check Your Browser for Security and Privacy Weaknesses
Runs entirely in your browser: Measures how unique your fingerprint is, tests WebRTC and IP leaks, checks whether your browser version is current, and probes which security policies it actually enforces.
Takes about five seconds. Signals are hashed before anything is sent, so we learn how common your browser is without learning what it is. What we keep
…
Your browser
Running checks…
Full detail: Everything we measured
Fingerprint uniqueness
Measuring…
…
How many browsers in our sample share your exact fingerprint.
About this checkSecurity policy enforcement
About these checksPrivacy signals
About these checksWhat scripts can see
About this checkRequest headers your browser sent
What this tool checks
16 checks across 1 areas. Each links to its reference page with the test, the risk and the fix.
Browser privacy and policy enforcement
16 checksThe ones that most often decide the grade:
High
Browser version is out of dateYour browser is behind the current stable release, so it is missing security fixes for bugs that attackers already...
Medium
Browser fingerprint uniquenessThe combination of signals your browser exposes matched no other visitor in our sample, so it could be used to...
Low
Canvas fingerprinting exposureYour browser renders a hidden test image identically every time and lets scripts read the pixels back, so the result...
Low
WebGL renderer exposureScripts can read your graphics card model and driver details through WebGL, a strong and long-lived identifying signal.
High
WebRTC IP address leakWebRTC revealed an IP address that differs from the one your connection uses, typically your real address behind a...
Info
Do Not Track signalYour browser is not sending the DNT: 1 header. Most sites ignore the signal in any case, so this is informational.
Low
Global Privacy Control signalYour browser is not sending the Global Privacy Control signal, so sites that are legally required to honour opt-outs...
Medium
Third-party cookies allowedYour browser accepts cookies set by third-party domains embedded in other sites, which is the basic mechanism of...
Low
Full referrer sent cross-siteWhen you follow a link to another site, your browser sends the full address of the page you came from, including its...
Medium
Browser enforces X-Frame-OptionsYour browser displayed a page inside a frame even though that page was served with X-Frame-Options: DENY, so the...
Medium
Browser enforces X-Content-Type-OptionsYour browser executed a script that was served with a non-script content type and X-Content-Type-Options: Nosniff,...
High
Browser enforces Content-Security-PolicyYour browser ran an inline script on a page whose Content-Security-Policy forbids it, so the cross-site scripting...
Low
Browser defaults cookies to SameSite=LaxYour browser sent a cookie that has no SameSite attribute on a cross-site request, so it does not apply the Lax...
Info
User-Agent Client Hints exposureYour browser answers high-entropy Client Hints requests, revealing its exact version, platform version, device model...
Info
Hardware details exposed to scriptsScripts on any page can read your CPU core count, approximate memory, screen geometry, touch capability and in some...
Info
JavaScript disabledJavaScript is off in your browser, so the client-side parts of this scan could not run. That is a strong privacy...
What the browser security and privacy check measures
The test combines browser version, network exposure, fingerprint uniqueness, privacy preferences and policy enforcement in one local session.
Websites learn more than a browser name. Scripts can observe screen dimensions, time zone, language, graphics hardware and supported features; together those ordinary values can form an unusual fingerprint. The browser also exposes network and policy behaviour that determines whether privacy tools and security controls work as expected.
The check runs in the browser you are currently using. Raw fingerprint signals stay on the page while hashes are compared with the observed sample. The connection address is compared with WebRTC candidates, the browser version is checked against vendor release data, and small policy tests measure whether important browser protections are actually enforced.
Measure locallyCollect supported browser, display, graphics and privacy signals.
Compare safelyHash fingerprint values and estimate how unusual the combination is.
Test protectionsCheck version, network leaks and security-policy enforcement.
Put this result in context
This scanner answers one part of the review. Continue with Extension Analyzer for permissions, host access, remote code, then WebRTC & IP Leak Test for real ip exposure behind a vpn. These are separate checks because a strong result here does not prove that the adjacent surface is healthy.
For the background behind these signals, read Browser Security: How Your Browser Is Attacked, Tracked and Hardened and Is My Browser Secure? A Practical Checklist. The Browser version is out of date check reference explains the exact test, evidence and remediation used in the report.
Browser checks and what they reveal
A privacy result is a combination of uniqueness, network exposure and browser behaviour.
| Area | What is measured | How to interpret it |
|---|---|---|
| Browser version | Reported browser family and version compared with current stable releases. | An outdated major version may be missing security fixes. |
| Fingerprint uniqueness | The combined rarity of hashed display, locale, graphics and capability signals. | A rarer combination is easier to recognise across visits. |
| IP and WebRTC | The normal connection address and public addresses revealed through WebRTC candidates. | Different public addresses can indicate a VPN or proxy leak. |
| Policy enforcement | Small CSP, mixed-content and related browser-policy behaviour tests. | Shows whether the browser enforces protections rather than only advertising support. |
| Privacy and hardware | GPC, Do Not Track and browser-visible CPU, memory, screen and GPU categories. | Explains what ordinary scripts can observe and which preferences they receive. |
How to read your browser result
There is no single private browser setting, so the report explains each contributing signal.
Update or leak detected
An outdated version, failed policy test or mismatched public WebRTC address needs direct attention.
Distinctive fingerprint
Uniqueness is a privacy observation, not malware. Extensions, unusual settings and rare hardware can all make a browser easier to recognise.
Improve browser privacy and security
- Install the latest stable browser update and enable automatic updates.
- Retest with the VPN enabled and review its WebRTC or leak-protection settings if public addresses differ.
- Remove extensions you no longer need and avoid stacking many fingerprint-changing add-ons.
- Use separate browser profiles or hardened modes for activities that need stronger isolation.
What this result does not prove
- A browser fingerprint changes as settings, extensions, hardware and the comparison sample change.
- The test cannot inspect browser source code, antivirus state or security controls outside the page sandbox.
- Privacy preference signals tell sites what you request; they do not prove that every site honours the request.
Related tools
Continue the review with four checks that cover adjacent parts of the same attack surface.
Browsers
Browser Extension Analyzer
Permissions, host access, remote code
Browsers
WebRTC & IP Leak Test
Real IP exposure behind a VPN
Privacy
Password Strength & Breach Checker
Breach lookup and strength analysis
Privacy
Phishing URL Checker
Lookalike domains and hidden redirects
Guides for this tool
Background reading written to go with these results.
12 min read · Updated Sep 12, 2026
Browser Security: How Your Browser Is Attacked, Tracked and Hardened
Your browser is the most exposed program on your computer. This hub explains the browser's security model, the ways it leaks identity...
Read the guide
8 min read · Updated Sep 05, 2026
Is My Browser Secure? A Practical Checklist
A secure browser is up to date, enforces the web's security policies, leaks little through WebRTC and fingerprinting, and runs only...
Read the guide
7 min read · Updated Sep 02, 2026
Browser Fingerprinting Explained: How Sites Identify You Without Cookies
Browser fingerprinting combines dozens of small facts about your browser and device into an identifier that survives cookie deletion and...
Read the guide
7 min read · Updated Sep 13, 2026
Why Browser Updates Matter: Zero-Days, Patch Gaps and Auto-Update
Browsers are patched every few weeks because attackers find exploitable bugs constantly. What a zero-day is, how long you are exposed...
Read the guide
7 min read · Updated Sep 11, 2026
WebRTC Leaks: How Your Browser Can Expose Your Real IP Behind a VPN
WebRTC lets browsers talk to each other directly, and to do that it discovers your network addresses, sometimes bypassing a VPN. The...
Read the guide
6 min read · Updated Sep 12, 2026
Cookies Explained: First-Party, Third-Party, SameSite and the Flags That Protect Them
Cookies keep you logged in and also follow you across sites. How they work, the difference between first- and third-party cookies, what...
Read the guideFrequently asked questions
Does this test send my data anywhere?
The fingerprint test sends only hashes of each signal, never the values, so we can estimate how common your combination is. The IP shown is what your connection already presents to every site.
Why is my fingerprint unique?
Combinations of screen size, fonts, GPU and time zone are individually common but jointly rare. The result page shows which signals contribute the most identifying bits.
Can you tell if my browser is up to date?
Yes. We read the version from your User-Agent or Client Hints and compare it with the current stable release from the vendors' own release feeds.
What do the policy-enforcement tests do?
They load small pages served with specific security headers and check whether your browser obeyed them, the approach BrowserAudit pioneered.
