Known limitations and fixed false findings

SpoofLens compares what a browser says about itself with what it shows. Some honest setups still trigger a finding: an antivirus that inspects HTTPS, a VPN, a work network, a trip abroad. This page lists the cases we know, what we changed and what such a finding means for you. If your browser is ordinary and a finding looks wrong, press "Is this a mistake?" under it.

Check your browser right now

Checking your browser…

Setups that can trigger a finding

An antivirus or a company gateway that inspects HTTPS talks to our server itself, so the server sees its TLS handshake, not the one of your browser. This shows as "TLS handshake not from a browser" and lowers the index by 12. To test the browser itself, switch HTTPS inspection off for a minute or try another network.
A VPN gives you a data center address: "data center or VPN address" lowers the index by 12. That is simply what a VPN looks like. DNS and WebRTC findings with a VPN on are real leaks, and the finding itself says how to close them.
A trip abroad with the home time zone, or a VPN in another country: the time zone does not fit the country of the IP address. It costs 12 as a mismatch, not 30 as a contradiction.
A proxy at work adds forwarding headers to your requests: 4.
Privacy protection in Brave, Tor Browser, Firefox with resistFingerprinting or Samsung Internet shows as protection with no penalty, not as a lie.
iCloud Private Relay is recognized from the list Apple publishes: the check shows it as protection and does not treat the relay address as a VPN.
Remote desktops and virtual machines: the Windows software renderer (Microsoft Basic Render Driver) is information only. Other software renderers, such as SwiftShader or llvmpipe, lower the index by 12.
Rules we are still testing show as information with no penalty until research devices confirm them.

What we fixed

Newest first. Each fix is also in the changelog.

29.10.2026, version 0.20.4: the Windows software renderer of remote desktops and virtual machines no longer lowers the index, and the desktop site mode of browsers on Android costs 12 instead of 30.
29.10.2026, version 0.20.3: an antivirus or a gateway that inspects HTTPS could look like Safari to our server and cost 30 as a contradiction. Outside Apple devices such a handshake now counts as not from a browser (12), with a note about antiviruses.
29.10.2026, version 0.20.2: home networks in Colombia, the UK, Italy and Brazil were marked as hosting. Starlink users in Ukraine got a time zone mismatch because Starlink addresses are registered in the US; the country now comes from the list Starlink publishes.
25.10.2026, version 0.16.2: a page opened inside a messenger on Android, the fingerprinting protection of Samsung Internet and Opera on Android tablets no longer get false findings.
23.10.2026, version 0.11.5: Chrome and Edge sometimes reported a zero-size window for a page they loaded in advance. The check now waits for the real size.
22.10.2026, version 0.10.2: an iPad in desktop website mode and Chrome on iPhone no longer get false findings.

How to report a finding

Press "Is this a mistake?" under the finding. You can tick what is on in your browser (a VPN, an antivirus that inspects HTTPS, a work network, a remote desktop) and add a short comment. If you tick "Attach this report", we make a shared report link without your IP address and network.

We keep the report for 90 days without your IP address and check the rule on research devices. A report does not switch a rule off by itself: people who use antidetect browsers press the button too.

Tools and guides on this topic

Frequently asked questions

Why does my honest browser get a finding at all?: The index measures whether a browser is consistent, not whether its owner is honest. Some honest tools change what our server sees (an antivirus, a VPN, a work proxy), and the check cannot know why. That is why such cases cost little and the text of the finding names the likely reason.
Do you remove rules that get many reports?: Not automatically. We check the rule on our research devices and change its condition if honest browsers trigger it. Every such change goes to the changelog.