Different public IP
A same-family WebRTC address differs from the observed HTTP address. This may be an IP leak, proxy rotation, or another network route.
Proxy WebRTC leak test.
Check whether WebRTC exposes a different public IP from your proxy connection. Open this page in the browser or proxy profile you want to test.
HOW TO USE THIS TEST
How to use this tool
Use the same browser profile and proxy settings you normally use. This test compares WebRTC with the HTTP address visible to our website.
- 01
Open the configured profile
Connect your proxy or VPN before starting. Changes to browser WebRTC privacy settings can change the result.
- 02
Gather WebRTC addresses
The browser creates a data channel and contacts our STUN endpoint to look for UDP server-reflexive candidates.
- 03
Compare public IPs
Review the HTTP address and any WebRTC candidates. A different address of the same family needs investigation; it is not automatically your real IP.
What each result means.
UDP address observed
STUN exposed a public UDP address. Matching addresses show no mismatch in this run, while IPv4 and IPv6 addresses cannot be directly equated.
No public candidate
WebRTC exposed no public UDP address. Privacy settings, permissions policy, or network restrictions can explain this; it does not prove that all UDP is blocked.
PROXY WEBRTC LEAK TEST FAQ
Understand your results.
No single check proves whether a connection is direct. Read the signals together.
Can WebRTC reveal an IP when I use a proxy?
Depending on the browser and routing setup, WebRTC can use a different path from normal web requests. Comparing a STUN public address with the observed HTTP IP can reveal that difference, but a mismatch alone does not establish which address is the user’s original IP.
Does this WebRTC test access my camera or microphone?
No. It creates a data channel and gathers ICE candidates. It does not request audio or video access.
Why are no public WebRTC addresses shown?
The browser may suppress candidates, WebRTC may be disabled, or the STUN request may fail. The result stays inconclusive for public IP exposure instead of claiming that every UDP request is blocked.
Does a matching IP guarantee there are no leaks?
No. It only means the measured addresses did not reveal a mismatch in this run. This test does not inspect DNS resolvers or all traffic from every application.