| STUN server | IP | Geolocation |
|---|---|---|
| | Checking… No IP address found |
| IP / address | Type | Description | Organization | Location |
|---|---|---|---|---|
| | ||||
| No WebRTC candidate addresses found. | ||||
Check what public IP addresses your browser exposes over WebRTC using multiple STUN servers, and compare them with your VPN or proxy address.
| STUN server | IP | Geolocation |
|---|---|---|
| | Checking… No IP address found |
| IP / address | Type | Description | Organization | Location |
|---|---|---|---|---|
| | ||||
| No WebRTC candidate addresses found. | ||||
WebRTC enables real-time audio and video. To set up a connection, a browser may collect local and public IP candidates. If WebRTC uses a different network path from your proxy or VPN, a site may see your public IP.
Each STUN server returns the public address it sees for a WebRTC connection. Compare the results across servers and with your HTTP public IP to identify potential differences in routing.
Install a WebRTC blocking extension (such as WebRTC Leak Prevent or the related uBlock Origin setting). In Firefox, go to about:config and set media.peerconnection.enabled to false to disable WebRTC entirely. You can also choose a VPN client with leak protection, which usually blocks the browser's STUN requests or forces them through the tunnel.
WebRTC uses ICE candidates to establish media connections. Compare the addresses found by the test with your expected network exit address when using a VPN or proxy.
Browsers can use mDNS hostnames to obscure local addresses. A hostname alone does not show the underlying private address in the test results.