Request public IP
Returns the address already visible to BrowserCheck's Cloudflare request. The browser does not call a third-party IP geolocation API.
Network address comparison
Browser Leak Test: Compare WebRTC and Public IP
This browser leak test compares two observations: the public IP address seen by BrowserCheck's web request and a server-reflexive address that WebRTC may obtain through STUN. A different address can reveal an unexpected network path, such as traffic that is not using the same VPN route.
A matching pair is narrower evidence. It means this WebRTC check did not expose a different public address in the current session; it does not prove that DNS, every IPv6 path, other applications or all WebRTC behavior is leak-free.
Live WebRTC and request-IP comparison
The request address comes from this site. The WebRTC address uses a STUN request and may be unavailable or privacy-masked.
- Request public IP
- Loading...
- WebRTC public address
- Checking...
- Address comparison
- No comparable address
- DNS / ports / Tor
- Not tested
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
What this browser leak test checks
WebRTC server-reflexive candidate
Creates a data-only peer connection and asks a STUN service for an ICE candidate. No camera or microphone permission is requested.
Exact address comparison
Labels exact text equality as a match and different comparable addresses as a mismatch. Missing values stay unavailable.
How to interpret a browser leak result
Different public addresses
Investigate VPN split tunneling, browser-specific proxy settings, IPv4/IPv6 routing and WebRTC handling. The result identifies a difference, not its cause.
Matching public addresses
No second public address was observed through this flow. This is not a universal no-leak certificate.
No WebRTC address
The browser may hide candidates, the STUN request may fail, WebRTC may be unsupported or network policy may block it. The result remains untested.
Leak tests not performed on this page
- DNS resolver requests are not generated or compared, so DNS leak status is not tested.
- Open ports and services on the device or router are not scanned.
- Tor Browser use is not asserted from a user agent or IP heuristic.
- VPN/proxy status, IP reputation and blacklists are not inferred from provider names.
- Traffic from other tabs, apps, extensions and protocols is outside this WebRTC flow.
Investigate a mismatch
- 1Record both displayed addresses and whether one is IPv4 and the other IPv6.
- 2Check the VPN or proxy documentation for WebRTC and split-tunneling settings.
- 3Repeat with the VPN disconnected only if doing so is safe for your situation, then compare the change.
- 4Use a dedicated DNS leak test and operating-system network tools for the paths this page does not cover.
Browser leak test FAQ
Does this WebRTC test use my camera or microphone?
No. It creates a data channel only and does not request camera or microphone permission.
Why is my local WebRTC address a .local name?
Many browsers use mDNS hostnames to avoid exposing a private LAN address directly. That is expected protective behavior, not a public-IP result.
Does a matching IP mean my VPN is perfect?
No. It covers only this web request and this STUN-derived WebRTC address. DNS, IPv6, split tunneling and other applications need separate verification.
Continue the privacy review
Inspect fingerprint surfaces and privacy signals separately, or verify the browser version before checking vendor settings.