Public IP
Confirm that websites see the proxy or VPN IP, not your original network.
After connecting to a VPN or proxy, test public IP, DNS leaks, WebRTC exposure, browser time zone, language, and fingerprint signals with NetScope.
Updated: 2026-05-11
A connected VPN client does not prove privacy. Check public IP, DNS resolver, WebRTC exposure, and browser fingerprint consistency after every major client or node change.
Confirm that websites see the proxy or VPN IP, not your original network.
DNS servers should not obviously reveal your original ISP or region.
Browser-level signals can still expose local network or inconsistent environment details.
Disable browser secure DNS or use the VPN/private DNS setting.
Change browser WebRTC privacy settings or use a hardened browser profile.
Retest with a stable node or VPN trial before relying on the route.
No. DNS, WebRTC, routing, and browser fingerprint signals can still expose unexpected details.
It depends on the use case, but long-term proxy or VPN use should avoid leaking DNS to the original network.
No. It is a diagnostic tool that reveals browser-visible signals; it does not promise anonymity or legal compliance.