WebRTC leak test for proxy & VPN users
WebRTC can expose local or real IP addresses through ICE/STUN even when HTTP traffic goes through a proxy. This test is built for CheckProxy.org users validating antidetect and proxy setups.
The scan runs entirely in your browser: RTCPeerConnection + STUN, ICE candidate analysis, and optional alternate IPv4/IPv6 checks. Results are indicative — combine with our proxy checker and DNS leak test.
Your remote IP
| IPv4 address |
—
|
|---|---|
| IPv6 address |
—
|
| IP classification | — |
| Country | — |
| IP trust score | — |
WebRTC support detection
| RTCPeerConnection | — |
|---|---|
| RTCDataChannel | — |
Your WebRTC IP
| WebRTC leak test | — |
|---|---|
| Local IP address | — |
| Public IP address | — |
Media devices
| Media Devices API | — |
|---|---|
| Audio capture permissions | — |
| Video capture permissions | — |
| Media devices | — |
Session Description (SDP)
—
FAQ — WebRTC leak test
Common questions about WebRTC, ICE candidates, and how local or reflexive IPs are detected.
A WebRTC leak is when the browser collects host or srflx IP addresses via ICE/STUN while the main connection uses a VPN or proxy path.
The tool creates an RTCPeerConnection with a STUN server, collects ICE candidates from SDP, and classifies host (local) and srflx (reflexive) addresses.
VPN clients route traffic differently depending on configuration. ICE/STUN may still use local interfaces or paths outside the tunnel depending on browser and VPN setup.
WebRTC uses ICE to collect host candidates from local network interfaces and srflx candidates from STUN server responses before establishing a peer connection.
Host candidates are addresses of local network interfaces. Srflx (server reflexive) candidates are public addresses returned by a STUN server for the current network path.
Results depend on browser, extensions, and network configuration. This tool provides an indicative snapshot of ICE candidates at test time.