METHOD, NOT MAGIC

How the score works.

The score is an educational privacy-posture indicator—not a security certification, anonymity guarantee, or vulnerability audit.

Network observations

Our server observes the address used to connect and checks its IP version. A metadata lookup estimates country, ASN, network operator, and whether public data sources associate the address with a VPN, proxy, Tor, hosting network, or abusive activity. These classifications are probabilistic.

Browser observations

JavaScript checks whether HTTPS is active, Global Privacy Control and Do Not Track are enabled, cookies are available, WebRTC exposes a literal private address, and common high-entropy browser surfaces are available. The test records no reusable browser fingerprint.

Scoring model

+15HTTPS connection
+12Global Privacy Control
+6Do Not Track preference
+12No literal WebRTC address leak observed
+8–15VPN, proxy, or Tor indicator
−4Broad high-entropy browser surface
−15Literal private address exposed through WebRTC

The model begins from a neutral baseline and is capped between 0 and 100. A higher score means fewer obvious signals in this limited test. It does not mean a user is anonymous.

Personas

Known limitations

Modern browsers often replace local WebRTC addresses with mDNS names, which is good but not conclusive. VPN databases can lag. Corporate gateways and mobile carriers can resemble proxies. Browser settings can change between private and normal windows. The test does not inspect extensions, malware, DNS resolvers, account tracking, or operating-system configuration.

← Run the test