GuardLayer Tools
REAL TEST
WebRTC
Is Your Real IP Leaking?
A clean, quick WebRTC leak check. We compare your baseline public IP with WebRTC ICE candidates
(what the browser may expose for real-time calls).
Note: “Leak” here means “extra network info exposed” — not hacking. Results depend on browser, VPN, extensions, and network.
Snapshot
Status: Ready
Updated: —
Connection Paths
What WebRTC reveals
—
Run the test to evaluate exposure
Baseline IP
—
IPv4: — • IPv6: —
WebRTC public candidate
—
If this differs from your baseline IP, it may indicate extra exposure paths.
WebRTC Support
—
RTCPeerConnection + DataChannel availability
Private / LAN
—
—
mDNS
—
—
Public candidates
—
—
Raw candidate lines
This is for troubleshooting. Some browsers hide local IPs via mDNS (privacy-friendly).
—
Optional STUN cross-check
If strict blockers block STUN, these may show “Disabled”. That’s okay — we still evaluate what your browser exposed.
What you can do
If you use a VPN, enable “WebRTC leak protection” (VPN app settings or browser extension).
If verdict is “Possible leak”, rerun in a clean browser profile (no extensions) for comparison.
Prefer browsers that keep local candidates private via mDNS (default in many modern browsers).
Remember: “Leak” ≠ hacked. It’s about what the browser shares for real-time connections.
