WebRTC is a browser communications technology
WebRTC enables real-time audio, video, and data communication in browsers. To establish peer connections it gathers network candidates. Those candidates can include local or public-facing network information depending on browser behavior, permissions, network topology, and privacy protections.
A local address is not the same as your public ISP address
Leak-test pages often display several addresses. Private addresses such as common 10.x, 172.16–31.x, or 192.168.x ranges are local network information and are not directly routable on the public internet. Modern browsers may also obscure local addresses. The important question is whether a public address that should be hidden by the VPN becomes available to the page.
Test in the browser you actually use
Connect the VPN, open a reputable test page, and compare the public address shown by ordinary web requests with any WebRTC candidates. Repeat in your normal browser profile because extensions and settings matter. If the browser exposes a different public ISP address while the VPN is connected, collect the result and investigate.
Do not disable browser features blindly
Blocking WebRTC entirely can break calling and conferencing applications. Prefer a VPN and browser configuration that handles routing correctly. If you change browser privacy settings, document the change and verify that the services you rely on still work.
Sources & further reading
This guide is general educational material. Platform behavior, provider policies, and network conditions can change. Check current documentation before relying on a specific configuration.
Report an error or suggest a clarification ↗