WebRTC Leak Test

Find whether WebRTC reveals a local or public address outside the expected browser path.

What this checks

  • The primary input or browser signal required by this tool.
  • Network, DNS, browser, or registry signals that are relevant to the tool result.
  • Basic consistency signals that help explain whether the result needs follow-up.

How to interpret results

  • Green or low-risk results usually mean the checked signal matches the expected network path.
  • Warnings mean the signal is incomplete, inconsistent, or needs another related tool for confirmation.
  • High-risk results should be verified with the related tools before making a blocking decision.

Common issues

  • Some results depend on third-party registry, DNS, browser, or network data and can be partial.
  • VPN, proxy, carrier-grade NAT, and browser privacy features can make signals appear inconsistent.

Privacy note

This tool should avoid persisting lookup inputs beyond the request needed to run the check. Draft tools do not run active checks yet.

Key Tools and References

Frequently Asked Questions

What is a WebRTC leak?

A WebRTC leak happens when your browser exposes network candidates that reveal local addresses, public addresses, or other interface details that are different from the IP a website sees over HTTP.

Does a WebRTC leak reveal my exact home address?

No. A WebRTC leak does not reveal your street address, but it can expose a private LAN address, a public IP address outside your VPN, or a separate IPv6 address that gives websites more network information than you expect.

Is an mDNS candidate a real IP leak?

Usually not. An mDNS candidate replaces a raw local IP with a temporary hostname ending in .local. That is safer than exposing the real LAN address, but it still shows that WebRTC host discovery is active.

Why can WebRTC show a different IP than the page sees over HTTP?

WebRTC gathers candidates from multiple network paths. If your browser, VPN, proxy, or IPv6 route behaves differently for peer connections than for normal web traffic, WebRTC can surface an address that does not match the HTTP exit IP.

Do I need camera or microphone permission for this test?

No. This test only creates a peer connection and gathers ICE candidates. It does not request camera or microphone access.