WebRTC Leak Test

A WebRTC leak occurs when your browser's WebRTC implementation reveals your real public IP address to websites, even when you are using a VPN or proxy service. WebRTC uses STUN (Session Traversal Utilities for NAT) servers to establish peer-to-peer connections, and during this process your true IP address can be exposed. This can be a potential privacy concern and other websites, advertisers, or malicious actors can exploit WebRTC to discover your actual location.

Not always. Many VPN services do not automatically prevent WebRTC leaks because the IP discovery process happens at the browser level, not the network level. Some VPN providers include built-in WebRTC leak protection in their browser extensions, but a standard VPN connection alone may not be sufficient. The safest approach is to disable WebRTC entirely in your browser settings.

There are several ways to prevent WebRTC leaks depending on your browser. In Firefox, you can type about:config in the address bar, search for media.peerconnection.enabled, and set it to false. In Chrome and Edge, you can install browser extensions such as WebRTC Leak Prevent or uBlock Origin, which include options to block WebRTC IP exposure. Keep in mind that disabling WebRTC entirely will break browser-based video calling applications like Google Meet or Discord.

Multiple public IP addresses in the results typically indicates that your device has more than one active network interface with a public IP, or that your VPN is leaking your real IP alongside the VPN-assigned IP. For example, if you are connected to a VPN but WebRTC discovers both the VPN server's IP and your true ISP-assigned IP, both will appear in the results. This is a sign of a WebRTC leak. In normal circumstances without a VPN, you should see only one public IP address matching your ISP connection.