IP & Privacy Guide

What Is a WebRTC Leak?

WebRTC enables real-time audio, video and peer-to-peer communication in browsers. To establish efficient connections, browsers may gather network candidates. A leak concern arises when this process exposes an address that a user expected a VPN or proxy to conceal.

What a test looks for

A WebRTC test asks the browser to collect connection candidates and reports addresses made available to the page. Run the Terbit WebRTC leak test before and after connecting to a VPN.

Local addresses versus public exposure

Private addresses such as those used inside a home network are not directly routable on the internet. Modern browsers may also replace local addresses with privacy-preserving hostnames. The most important warning is exposure of the normal public address when you expected only the VPN address to appear.

Why results differ

Browser version, operating system, extensions, VPN design and network configuration can change the candidates returned. A blank or limited result may mean the browser has restricted discovery; it does not prove that every form of tracking is blocked.

How to reduce unwanted exposure

Update the browser and VPN application, enable the provider’s leak-protection setting and retest. Some browsers or extensions allow tighter WebRTC controls, but disabling WebRTC may break calls and collaboration tools. Prefer a documented control over an unknown extension.

Test more than one layer

Also verify the visible public IP address and run a DNS leak test. Remember that cookies, sign-ins and browser fingerprinting can identify activity even when the network address is masked.

When to contact the provider

If your normal public address remains visible with the VPN connected, capture the browser, operating system, test time and result, then ask the VPN provider for configuration guidance.

Reviewed 10 September 2026. Test output is diagnostic information and does not guarantee anonymity or VPN performance.