Browser Compatibility
If your browser suppresses WebRTC or masks local addresses with mDNS hostnames, this page will show that directly.
WebRTC Leak Test
Check whether your browser exposes local IP details.
This page targets webrtc leak test, webrtc leaktest, and related local IP exposure queries. It gathers ICE candidates in your browser and shows whether direct local IPs, mDNS hostnames, relay paths, or public candidates are visible.
The earlier mirrored page relied on a large external lookup setup. This rewritten version focuses on the direct browser evidence instead, which is lighter, more transparent, and easier to maintain across browsers.
The test runs locally in your browser and does not upload your ICE candidate list to router.fyi. Results depend on your browser, operating system, network path, VPN usage, and WebRTC privacy settings.
Ready.
OutcomeWaiting to test
Direct local IPs0
mDNS names0
Total ICE candidates0
What this test checks
Direct private IP exposure such as
192.168.x.x, 10.x.x.x, or 172.16-31.x.x.mDNS-style local placeholders ending in
.local, which often means the browser is masking direct local IPs.Other ICE candidate details such as protocol, type, related address, and relay behavior.
Exposure Summary
webrtc leak test
ip leak test
browser privacy
Run the test to inspect your current browser's ICE candidates.
WebRTC Diagnostics
candidate types
tcpType
related address
Run the test to see additional ICE diagnostics.
ICE Candidates
| Address | Protocol | Type | Foundation |
|---|---|---|---|
| No ICE candidates yet. | |||
Raw Candidate Lines
Waiting for test.
FAQ
What does it mean if I only see .local hostnames?
That usually means the browser is masking direct local IP exposure with mDNS hostnames. It is generally a better privacy outcome than showing the private IP directly.
What does it mean if direct private IPs appear?
It means the browser exposed local network details directly in ICE candidates. That is the classic WebRTC local IP leak behavior many users are trying to test for.
Why is this page lighter than the mirrored legacy version?
The legacy mirror depended on a very large lookup dataset. The rewrite focuses on the direct ICE evidence the browser already gives you, which is enough for the core leak-test question and is much more practical to ship.