Tools/WebRTC Leak Test

WebRTC Leak Test

Check whether WebRTC exposes public or local network details.

Dev + Network

Public IP

Exposed IPs

mDNS masked

Status

Type	Address	Source

Results can change when you switch browser, VPN, or network.

Tip: double-click any visible result to copy it to your clipboard.

Privacy check

Check whether your browser leaks network details through WebRTC.

Check what this browser shares through WebRTC before and after you change VPN, browser, or privacy settings.

Highlights

Run it before and after connecting to see whether candidate exposure changes with your current setup.

Compare browsers or profiles to spot which one exposes more network detail.

Grab a summary for troubleshooting without pasting raw ICE logs into a ticket.

Run it before and after changes to see what really shifts.

Tooloh checks WebRTC candidates and compares them with your current public IP.

Check whether the session reveals public IP, local addresses, or only masked hostnames.

Rerun after toggling VPN, browser flags, privacy extensions, or network paths.

Same vibe. Same speed.

Quick answers. No walls of text.

Does public IP exposure always mean something is broken?

Not always. The point is to show what the current browser session exposes so you can decide if that matches your privacy expectations.

Why do I see .local names instead of IPs?

Many browsers use mDNS obfuscation to avoid exposing direct local IP addresses to websites.

Can a VPN or extension change the result?

Yes. Browser settings, enterprise policy, privacy extensions, and VPN modes can all change which candidates are exposed.