How PowerScan works
Last updated October 26, 2026
Everything is measured in your browser. A few lookups need an outside service, and each one is named below.
What it reads
Your user agent and Client Hints, screen size and pixel ratio, time zone and languages, hardware concurrency and device memory, Canvas, WebGL, audio and font behaviour, and WebRTC addresses. These values stay in memory in your browser and are never stored or sent.
Outside lookups
Your public IP and rough location come from ipwho.is. The WebRTC check sends one standard STUN request to Google. The proxy verdict uses proxycheck.io and iplocate.io, and the blacklist check asks Cloudflare's public DNS about ten public spam lists. Each of them sees your IP address, like any site you visit.
The score
It counts how many checks returned a value and whether the values agree: time zone against IP location, language against headers, platform against user agent. Every disagreement is listed as a deduction, with its reason.
What it cannot see
Private-window detection and a full DNS leak test are not possible from a page script, so they show as Not tested. When a lookup is blocked, the line says Unavailable instead of guessing.
Opened by PowerOps
When PowerOps opens this page for one of its profiles, it adds the profile's name, number, engine, time zone, locale and screen after the # in the address. The part after # never leaves your browser; only this page reads it, to label the report.