Do you create a fingerprint ID?

No. The page reads standard browser fields locally and does not hash them into a tracking identifier or store them on a server.

Why is JavaScript shown as enabled?

These checks require JavaScript to run in your browser. If it were blocked, this interactive tool would not load.

Does a low privacy score mean my VPN failed?

No. The score lists locally observed signals such as cookies or WebGL. It is not a VPN test and cannot prove whether a VPN is on.

Local browser signals

Browser privacy test

These fields are read with ordinary web APIs in this browser. Run the privacy test below to collect them. This page does not build a fingerprint ID.

View current NordVPN offer

Affiliate link — we may earn a commission.

Public IP

This lookup runs in your browser so the address is yours, not the address of our hosting server.

Looking up your public IP from your browser…

Privacy score

Idle

Run the privacy test to calculate a score.

How this score is calculated

The score starts at 100. Each deduction below is a locally observed signal, not a medical, legal, or absolute security claim. A typical browser will not score 100. Private/local WebRTC addresses and a matching public IP are not counted as leaks.

Browser privacy signals

These values are read locally in your browser. No fingerprint ID is created and nothing is stored on a server.

Run the privacy test to calculate a score.

Session report

Copy a plain-text summary for yourself. Your raw IP is never placed in a public share URL — this app does not create share links.

What this tool does not do

It cannot prove that a VPN, proxy, or Tor is in use.
It does not test DNS leaks or malware. A visible public IPv6 address is not a VPN leak by itself.
It is not a security audit, legal advice, or a guarantee of privacy.
Location fields are only shown when a free lookup provider actually returns them.

What is collected, and where it stays

User agent, language, timezone, screen resolution, Do Not Track, cookie availability, WebGL vendor/renderer, JavaScript, and referrer are typical values a website can already read. This app lists them for you instead of hiding them behind a score-only widget.

Nothing is sent to a profile database here. The optional text report is copied on your device. A typical browser will still expose several of these signals; that is expected, not a verdict that you are “unsafe.”

Limits of a page-level check

This is not a full anti-fingerprinting audit, not a VPN detector, and not a DNS test. WebGL or cookie details do not prove a VPN is enabled. Use the WebRTC and VPN comparison tools if you want those separate checks.

Related guide

A written walkthrough for the situation this tool is often used to check.

How to interpret and reduce a WebRTC leak

A longer explanation of what this check can show — and what it cannot prove.

Browser fingerprinting explained

Other local checks

These pages reuse the same browser-side checks. None of them can prove that a VPN is enabled.