LuabifyQuick device diagnostics

WebRTC Leak Test: Check Public and Local IP Candidates

Click WebRTC leak test Check whether your browser exposes public, local, or obfuscated WebRTC candidates and compare them with your current public IP.

Browser privacy

WebRTC Leak Test

Check whether your browser exposes local or public network candidates through WebRTC.

Ready to scan

This browser-based test gathers ICE candidates with a public STUN server. Results depend on browser, VPN, extensions, and network policy.

Leak test results

Run the test to inspect WebRTC candidates.

Exposure summaryNo scan yet
Browser support--
Current public IP--
Candidates found0
Public candidates0
Assessment

Run the test to inspect what WebRTC exposes in this browser.

Detected WebRTC candidates will appear here after the scan.

Why run a WebRTC leak test online

A WebRTC leak test helps you see what network information the browser exposes while gathering ICE candidates for calls, meetings, screen sharing, and peer-to-peer apps. It is especially useful when you rely on a VPN, browser privacy settings, hardened extensions, or network policies and want to confirm whether WebRTC is still revealing a public-facing path, a local address, or only obfuscated candidates.

How the test runs

The tool creates a temporary WebRTC connection in the browser, gathers ICE candidates with public STUN servers, and lists the addresses the browser exposes during that process. It also reads your current public IP through a standard web request so you can compare what WebRTC exposes with what a normal website sees. The test is browser-based and does not require a call, camera, microphone, or account login.

How to interpret results

If a public candidate appears, the browser exposed a public-facing network path during WebRTC gathering. If that public candidate differs from the current public IP shown by the page, that can indicate another exposed path, alternate routing, or a VPN leak scenario worth reviewing. If only local or obfuscated candidates appear, exposure is narrower but still relevant for privacy-sensitive setups, and if no candidates appear, the browser, VPN, extension, or network policy may be limiting WebRTC candidate gathering.

  • Public candidates mean WebRTC exposed an internet-facing address or route.
  • Local candidates show private interface details that may still matter in privacy-sensitive workflows.
  • Obfuscated candidates usually mean the browser replaced local IPs with mDNS hostnames.
  • A public candidate different from the current public IP can indicate another exposed network path.
  • No visible candidates suggests stronger masking, but it does not guarantee anonymity.

This test reports what the browser exposes during ICE gathering at that moment. It does not inspect TURN infrastructure, decrypt traffic, bypass VPN protections, or prove that every privacy risk is eliminated when no candidate appears.

Related tools

Frequently Asked Questions

What does this WebRTC leak test check?

This WebRTC leak test checks which ICE candidates your browser exposes during temporary WebRTC candidate gathering. That can include public, local, or obfuscated addresses depending on browser, network, and privacy setup.

Can WebRTC expose my real IP address?

Yes, in some setups WebRTC can expose a public-facing candidate that reveals an address or route you did not expect. The exact result depends on browser behavior, VPN design, and how local network candidates are handled.

Why does the page compare WebRTC candidates with my current public IP?

That comparison helps detect when WebRTC exposes a public candidate that differs from the IP shown in a normal web request. In some VPN or split-routing setups, that can reveal an alternate visible network path.

What is an ICE candidate?

An ICE candidate is a possible network path WebRTC can use for audio, video, or data connections. Browsers gather these candidates from local interfaces, STUN responses, and sometimes relay infrastructure.

What is the difference between public, local, and obfuscated candidates?

Public candidates point to internet-facing network paths, local candidates reflect private interface details, and obfuscated candidates usually replace local IPs with mDNS hostnames. Public exposure is generally the most sensitive result in a VPN privacy check.

What does it mean if only local or obfuscated candidates appear?

It usually means the browser did not expose a public-facing candidate during the check, but it still exposed some local WebRTC path information. That is often better than a public candidate leak, but it may still matter in stricter privacy environments.

What if no candidates appear in the results?

That usually means WebRTC candidate gathering was limited by the browser, an extension, a VPN, or network policy. It is a positive sign for masking, but it does not prove complete anonymity across all privacy layers.

Can a VPN still leak through WebRTC?

Yes. Some VPN setups still allow public or local candidates to appear, especially when browser privacy settings are permissive or leak protection is incomplete. That is why checking both the candidates and the current public IP matters.

Does this WebRTC leak test need microphone or camera access?

No. The test only gathers WebRTC network candidates and does not need a camera or microphone permission prompt to run. It is a network exposure check, not a media permission test.

Does this mean WebRTC is unsafe?

Not by itself. WebRTC is a legitimate browser technology for calls, meetings, and peer-to-peer features, but candidate exposure can matter when your goal is to minimize visible network information.

Can this tool prove that I am fully anonymous?

No. Even if no candidates appear, privacy still depends on DNS behavior, cookies, browser fingerprinting, account logins, extensions, and other network characteristics. This page only checks WebRTC candidate exposure.

When should I run this WebRTC leak test online?

Use it after enabling or changing a VPN, adjusting browser privacy settings, testing a privacy extension, or checking whether a browser setup is exposing more network information than expected. It is also useful before relying on a browser in privacy-sensitive situations.