Install from the Chrome Web Store (free, version 1.0.8, store listing in 19 languages, interface in English).
Prefer to test without installing anything? Run the same IP, WebRTC and DNS checks in the page: IP, WebRTC and DNS leak test on vpnsmith.com.
One click tells you whether your VPN really hides your IP:
webRTCIPHandlingPolicy to disable_non_proxied_udp).Built by the team behind vpnsmith.com. No analytics, no servers. See PRIVACY.md.
chrome://extensions, enable Developer mode.python3 tools/pack.py # writes dist/vpn-leak-guard-<version>.zip
manifest.json (MV3), popup.html|css|js, background.js (service worker), config.js (every outbound link).store/: listing copy and permission justifications.Measured while building the extension (Chromium, Manifest V3, October 2026): after
chrome.privacy.network.webRTCIPHandlingPolicy is set to disable_non_proxied_udp, an ordinary
site such as example.com gathers no WebRTC candidate, but the extension’s own popup still gathers
both the host and the server-reflexive (srflx) candidates. Chrome does not apply that policy to
extension pages. A popup that tested itself would keep reporting a leak that websites can no
longer see, so the popup labels the state “blocked on sites” and links to a real web page for the
proof. If you build a WebRTC blocker, test the policy from a normal tab, never from
chrome-extension:// pages.
Chrome and Chromium-based browsers only for now. In Firefox you can turn WebRTC off without an
extension (media.peerconnection.enabled = false in about:config), then confirm with the
leak test.