How to fix a possible WebRTC leak

First compare the WebRTC public addresses with the public exit IP you intended to use. A different public address may need investigation; a private address or an mDNS name alone does not prove that your public IP leaked.

What can you change?

Check the VPN application’s supported leak protection and browser network settings. WebRTC is also used by calls and conferencing, so disabling it can break those features. A failed or blocked test is unknown, not proof of protection.

Steps

1. Record the exit IP and the observed WebRTC address type.
2. Change one supported VPN or browser setting at a time.
3. Run the check again on the same connection, then verify that calls still work.

FAQ

Will fixing WebRTC improve the IP score?

No. Browser observations do not change the server IP score. Check the browser observation again to evaluate the change.

Related diagnostics

Modern home, IP risk, privacy and latency pages start a shared session automatically, including external DNS and STUN connections. Direct entry to tools, method or policy pages does not start a session; an existing session may continue. Old language homepages show an IP profile and use separate buttons for extra browser checks. Guides are explanations, not test results.