Whoer's anonymity percentage blends IP, DNS, WebRTC and timezone checks with unpublished weights — and the company scoring you also sells the fix.
Run a browser through Whoer.net and you get back a single number: an anonymity percentage out of 100, with a green, yellow, or red verdict attached. It looks like a measurement. It's presented like one, with a clean progress bar and a breakdown of "checks passed." But no standards body defines what an anonymity percentage is, and the company printing yours also sells a product that raises it. Neither fact makes the underlying checks useless — most of them are real. It does mean the number on the page is doing a different job than it appears to.
Key Takeaways
- Whoer.net is a VPN vendor (Whoer VPN, a paid subscription product) whose free anonymity-score page sits at the top of its own funnel — this isn't a neutral third-party audit.
- The percentage blends real, individually verifiable signals — IP/ASN, DNS resolver location, WebRTC exposure, timezone-vs-IP match, hosting-range heuristics — but the weights combining them into one number are unpublished and vendor-chosen.
- Because the weighting is private, a different vendor scoring the identical browser produces a different number for it — this is the same phenomenon covered in Why Fingerprint Test Tools Disagree About You, just for anonymity composites specifically.
- When the party computing your score is also the party selling the fix, the score functions as a marketing instrument as well as a diagnostic — worth knowing, not worth panicking over.
- Each underlying signal can be checked independently, with the reasoning shown rather than collapsed into a percentage — that's a more useful reading than the top-line number.
What Whoer.net Actually Is
Whoer.net runs a paid VPN service under the same brand, and the free anonymity-checker page is the entry point to it: run the check, see a percentage that reads as unimpressive, and the upsell to the paid product sits right below the result. This isn't a hidden fact — it's stated on the site — but it's easy to miss when the checker page itself looks like a plain diagnostic tool, and it matters for how to read the number. Whoer's checker is also a fixture inside the antidetect-browser ecosystem, where multi-account operators use it as a pass/fail gate before touching a platform, which is a separate use case from an ordinary reader asking "am I actually private right now."
None of that makes the individual checks fake. It means the percentage that summarizes them is produced by a company with a direct financial interest in two things at once: the number looking bad enough to worry about, and the product it sells looking like the way to fix it. Worth holding in mind before treating a single score as an objective verdict.
The Signals Under the Percentage
Strip the percentage away and what's actually being tested is a short list of real, well-understood signals:
- IP address and its ASN/organization — whether the address you're browsing from belongs to a residential ISP, a datacenter, or a known hosting range. Datacenter and hosting IPs score as lower-anonymity, on the reasoning that ordinary consumer browsing rarely originates from them.
- DNS resolver location versus IP location — if the resolver handling your DNS lookups sits in a different country or network than your browsing IP, that split is a coherence signal. It's grown more common since DNS over HTTPS made it normal for a browser to send lookups to a fixed public resolver regardless of which network it's on — the same kind of split covered in DNS Leak Prevention: Hide Your Browsing Footprint.
- WebRTC local and public address exposure — the WebRTC API can surface a device's real local network address, and in some configurations its real public IP, independently of whatever address the page's main connection shows. WebRTC Leak Protection: A Must for VPN Users covers the mechanism in full.
- Timezone and locale versus IP geolocation — a browser's reported timezone and language settings are compared against where the IP address geolocates to; see Timezone and Locale Leaks: When Your Browser Contradicts Your IP for how that mismatch gets flagged.
- Proxy and hosting-range heuristics — IP ranges get cross-referenced against known VPN, proxy, and cloud-hosting blocks, which is one input into how confidently a location can be trusted in the first place; see IP Geolocation: Balancing Accuracy and Privacy for how that confidence is actually derived.
- Other browser-reported values — user-agent, screen and font data, and similar attributes get folded in as supporting signals alongside the network-level checks above.
Each of those is a legitimate, independently verifiable thing to check — and most of them you can read off for yourself right now, unweighted, with BrowserInsight's VPN and proxy check. The problem isn't the inputs. It's the next step, where they get combined.
Why the Same Browser Gets a Different Number From a Different Vendor
Turning six-plus separate signals into one percentage requires a weighting scheme — how much a WebRTC leak should cost you relative to a timezone mismatch, how a datacenter IP should be penalized against a clean residential one. That weighting isn't published, isn't standardized across the industry, and can change between product versions without any changelog a visitor would see.
That's exactly the mechanism Why Fingerprint Test Tools Disagree About You describes for vendor anonymity composites generally: a single vendor's percentage reflects that vendor's private recipe, not a shared unit of measurement. Run the identical browser, on the identical connection, through two different anonymity checkers, and you can get two different percentages — not because one tool is wrong, but because each is free to weigh the same inputs however it chooses. Treat any single vendor's number as that vendor's opinion about your setup, not a portable score you could hand to someone else and expect them to interpret the same way.
The Score Grades Its Own Fix
Worth stating plainly, once: the entity computing your anonymity percentage is the same entity selling the VPN subscription that's positioned to raise it. That's not an accusation of dishonest math — the underlying checks described above are real and technically sound. It's a structural fact about incentives. A free diagnostic that sits directly above a paid upsell has a reason to produce a number that reads as "concerning enough to act on," and because the weighting is never published, no outside party is in a position to confirm it's free of that pull. Read the percentage as a marketing instrument as well as a diagnostic, and move on to what you can verify yourself.
What to Check Yourself Instead of the Percentage
The more useful move is to check the individual signals directly, where you can see the reasoning rather than a single collapsed number:
- Run BrowserInsight's VPN and proxy check to see your IP's ASN, hosting classification, and WebRTC/DNS leak status laid out as separate results.
- Run the IP check to see exactly what your IP address reveals about location and network ownership, and how confidently.
- Read WebRTC Leak Protection and DNS Leak Prevention for how each specific leak happens and how to close it, independent of any vendor's summary score.
- Read Timezone and Locale Leaks if you want to understand that particular mismatch before a single combined percentage flags it for you.
None of this is a guide to making any vendor's number go up — it's a way to see what's actually true about your connection, signal by signal, without taking one company's private weighting on faith.
Frequently Asked Questions
Is Whoer.net's anonymity score fake or rigged?
No. The underlying checks — IP/ASN, DNS resolver location, WebRTC exposure, timezone match — are real and technically legitimate. What's not published is how those checks get combined into one percentage, and the company doing the combining also sells a product that raises the result.
What's a "good" Whoer anonymity score?
There's no standard answer, because there's no standard for what the percentage measures — it's one vendor's private weighting of several signals. A more useful question is whether each individual signal (IP type, DNS resolver location, WebRTC exposure, timezone match) looks the way you expect, which you can check directly rather than through a single blended number.
Why do different anonymity checkers give my browser different scores?
Because each vendor weighs the same underlying signals differently, and none of those weightings are standardized or published. Why Fingerprint Test Tools Disagree About You covers this same pattern across fingerprint and anonymity tools generally.
Should I trust an anonymity percentage from any VPN-adjacent site?
Treat it as that company's opinion about your setup rather than an objective measurement, especially when the same site sells a product positioned to improve the number. The individual signals behind the score are usually worth checking; the single collapsed percentage usually isn't the most useful part of the page.
