Free Browser Privacy Tool
WebRTC Leak Test
Check whether WebRTC can expose your real local or public IP address while you are using a VPN, proxy server, NAT network, or DICloak antidetect browser profile.
Your WebRTC Leak Test
Run the WebRTC leak test to check browser support, candidate IPs, the SDP log, and media device behavior.
Your Remote IP
WebRTC Support Detection
Your WebRTC IP
Session Description
Media Devices
What Is a WebRTC Leak Test?
A WebRTC leak test checks whether browser WebRTC features can reveal network details that differ from the IP address shown by normal web traffic. It is especially useful for VPN, proxy, NAT, and antidetect browser users who need to verify that their real IP address is not exposed.
What This Tool Checks
- Your remote IPv4 address as seen by this page.
- Whether RTCPeerConnection and RTCDataChannel are available in the browser.
- Local, public, IPv6, and mDNS WebRTC candidates returned by ICE gathering.
- Whether the WebRTC public IP differs from the remote IP.
- The raw SDP log generated during the WebRTC session.
- Media Devices API support and optional audio/video permission behavior.
How to Read the Results
- No Leak means no local IP and no mismatched public WebRTC IP were found in this run.
- Leak Detected means WebRTC exposed a local IP address or a public IP that differs from your remote IP.
- mDNS candidates such as .local names usually mean the browser hides the local IP, but WebRTC is still enabled.
- WebRTC Disabled means the browser blocks RTCPeerConnection, which can reduce leak risk but may affect real-time communication sites.
How to Disable WebRTC
If WebRTC exposes your real IP while using a proxy or VPN, limit or disable WebRTC in the browser or use a DICloak profile with controlled WebRTC settings.
WebRTC in Firefox
- Open about:config in the Firefox address bar.
- Search for media.peerconnection.enabled.
- Set the preference to false, then reopen this page and run the test again.
WebRTC in Chrome and Edge
- Chrome and Edge do not provide a single built-in switch for every WebRTC leak scenario.
- Use a trusted WebRTC control extension or a managed browser profile.
- Run this test again after changing the profile or extension settings.
WebRTC in Brave
- Open Brave privacy settings.
- Find WebRTC IP handling policy.
- Choose a stricter policy if you use proxies or VPNs, then rerun the leak test.
WebRTC in Safari
- Keep Safari updated and check experimental feature settings if WebRTC behavior changes.
- Use this test after profile or VPN changes to confirm whether candidates are exposed.
How to Prevent WebRTC Leaks in DICloak
DICloak browser profiles can help keep proxy, timezone, language, canvas, WebRTC, and other fingerprint settings aligned. After changing a profile, run this test again to confirm that the environment does not expose unexpected WebRTC IP data.
- Open the DICloak profile you want to use with a proxy or VPN.
- Go to the fingerprint or WebRTC settings for that browser profile.
- Choose the WebRTC mode that matches your proxy strategy and account risk level.
- Save the profile, reopen the browser environment, and run this WebRTC leak test again.
- Use Anonymous Check for a broader privacy and fingerprint consistency review after WebRTC is configured.
WebRTC Leak Test FAQ
What is a WebRTC leak?
A WebRTC leak happens when WebRTC exposes a local IP address or a public IP address that differs from the IP shown by normal web traffic. This can reveal network information even when a VPN or proxy is active.
Can WebRTC reveal my real IP address?
Yes. Depending on browser settings, VPN behavior, proxy setup, and STUN candidate collection, WebRTC may reveal local network addresses or a public IP that does not match your expected browsing IP.
Why do I see a .local mDNS address?
Modern browsers often replace local IP addresses with mDNS hostnames ending in .local. This helps hide the exact local IP, but it still indicates that WebRTC candidate gathering is enabled.
Should I disable WebRTC completely?
If you rely on proxies, VPNs, or isolated browser profiles for privacy, disabling or strictly controlling WebRTC can reduce leak risk. Some video chat and real-time collaboration sites may need WebRTC to work.
Does DICloak help prevent WebRTC leaks?
DICloak lets you manage WebRTC and other fingerprint settings inside browser profiles. The best practice is to configure the profile, open it with the intended proxy, and rerun this test to verify the result.