How to Use the WebRTC IP Leak & Local Network Detector
-
1
Click "Start WebRTC Leak Test" to initiate candidate gathering.
-
2
Review discovered Public IP addresses discovered via STUN servers.
-
3
Check discovered Local / LAN IP addresses (e.g. 192.168.x.x, 10.x.x.x, or mDNS .local identifiers).
-
4
Review the VPN leak audit indicator to ensure your real IP is not bypassing your active VPN tunnel.
-
5
Copy the technical report or export diagnostic results.
Practical Example & Use Case
Common Real-World Scenario
Verifying that your active commercial VPN or privacy proxy is correctly masking your actual residential IP without leaking through WebRTC audio/video peer connections.
Technical Notes & Limitations
Browser Engine Architecture
Modern browsers use mDNS anonymization (.local UUIDs) by default for local interfaces unless microphone permissions have been granted.
Frequently Asked Questions
What is a WebRTC IP leak?
WebRTC uses STUN (Session Traversal Utilities for NAT) servers to discover your direct IP address for peer-to-peer media. In poorly configured browsers, this can expose your real ISP IP even when using a VPN.
Does this tool send my IP to any third-party server?
No! Candidate gathering is executed natively in your browser using standard public STUN servers (Google STUN). All evaluation is rendered strictly in client memory.