VPN Leak Test
Run the broader VPN privacy diagnostic.
Open VPN Leak Test
WebRTC Privacy Test
WebRTC Leak Test
Check whether your browser exposes an additional public IP address through WebRTC.
First-party STUN · No camera or microphone access
Your connection
Detecting
…
Detecting your connection…
WebRTC path check
This test uses your browser’s WebRTC networking API and IPRevealed’s first-party STUN server.
Checking your WebRTC path
- Reading public connection
- Starting WebRTC
- Gathering ICE candidates
- Comparing network paths
We couldn’t complete the WebRTC test.
Try the test again.
Normal web connection ↔ WebRTC
Normal web
WebRTC
ICE candidates
| Address | Candidate type | IP version | Scope | Protocol |
|---|
What we observed
Technical details
Host candidate — an address gathered directly from a local network interface, without contacting any server.
Server-reflexive candidate (srflx) — the public address and port a STUN server observed your connection using.
mDNS — a randomized .local hostname some browsers substitute for a local host address as a built-in privacy protection.
Understand WebRTC privacy
WebRTC itself is not inherently a leak — here’s what it can and can’t tell you.
WebRTC basics
What is WebRTC?
WebRTC is a browser API for real-time audio, video and data connections directly between peers. To find the best path between two devices, it gathers a list of network addresses called ICE candidates — this test reads that list without opening any media stream.
How it works
Why can WebRTC reveal IP addresses?
Establishing a direct peer connection requires knowing real network addresses. A STUN server tells the browser its public-facing address (a server-reflexive candidate), which is generally the same address seen by any website you visit — it becomes notable mainly when it differs from that address.
Browser privacy
What does mDNS hide?
Modern browsers commonly replace a device’s local network address with a randomized .local hostname instead of exposing it directly. Seeing an mDNS hostname is normal, built-in browser privacy behavior, not a fault.
Limitations
Can a VPN leak through WebRTC?
Sometimes. If a VPN doesn’t route all UDP traffic through its tunnel, WebRTC’s STUN request can expose your ISP-assigned address alongside or instead of the VPN’s. A private LAN address alone is not a leak — the concern is a differing public address.
How this test works
- 01 Read normal connection Your current public IP is read the same way any website sees it.
- 02 Create local connection Your browser opens a local RTCPeerConnection with a dummy data channel.
- 03 Contact first-party STUN IPRevealed’s own STUN server reports the address it sees — no third-party STUN.
- 04 Inspect candidates locally All ICE candidates are parsed and classified in your browser.
- 05 Compare paths The WebRTC path is compared with your normal web connection.
Continue checking your connection
Each tool inspects a different part of what your connection or browser can reveal.
DNS Leak Test
Check DNS resolver exposure.
Open DNS Leak TestIP Lookup
Inspect the IP address or network you observed.
Open IP Lookup