DuoPlus Free Tools

WebRTC Leak Test

Checking

For VPN and proxy users, this test checks whether WebRTC ICE candidates expose network addresses on a different route. It gathers candidates through STUN and compares public mappings with the IP address seen by this page.

—

Looking up your public IP…

WebRTC API

Checking browser support…

Microphone permission

Not needed for this test

Camera permission

Not needed for this test

How this test works

When this page loads, your browser sends requests to the public STUN providers listed below; those providers can observe your network IP. Candidate addresses are displayed on this page and are not uploaded to DuoPlus. The page also requests your current public IP from the DuoPlus network lookup API for comparison. No camera or microphone permission is requested.

The test starts automatically when this page loads.

STUN Service Results

ICE candidates are gathered from several STUN services. Expand a candidate log to inspect the raw details.

How can I limit WebRTC?

If you want to reduce the chance of WebRTC exposing network addresses, adjust your browser's WebRTC settings. Disabling or limiting WebRTC may affect voice calls, video calls, and other real-time features.

Firefox (desktop)

Enter about:config in the address bar to open the advanced configuration page.
Search for media.peerconnection.enabled and switch it to false.

This disables RTCPeerConnection and may prevent web voice or video calls from working. Set it back to true to restore WebRTC. Settings can vary by version and platform.

Chrome

Chrome's regular settings do not provide a simple WebRTC off switch. Google's extension can adjust the network interfaces and UDP traffic used by WebRTC.

View Google WebRTC Network Limiter

Limiting WebRTC may affect call quality or make some real-time features unavailable. Check the publisher and requested permissions before installing an extension.

How can WebRTC reveal network addresses?

WebRTC uses ICE to establish connections. A browser can use STUN services to discover mapped addresses: host candidates generally represent a device network interface, srflx candidates represent a public mapping observed by STUN, and relay candidates represent a relayed address. Public host, server-reflexive, or peer-reflexive candidates can expose an address to a page. If one differs from the IP above, WebRTC may be using a different route.

Interpreting the results

A public WebRTC candidate means the address is visible to this page. A candidate that differs from the IP seen by this page may indicate a VPN or proxy route mismatch. A matching address does not prove that WebRTC is hidden or that it matches the VPN exit you intended to use. Results can differ across sites because they use different STUN servers and leak criteria. Browser privacy settings, network conditions, firewalls, and STUN availability also affect results.