If you are connected to a VPN and in the Web RTC: section you see your ISP IP, then your system is leaking WebRTC requests
Additionally, these STUN requests are made outside of the normal XMLHttpRequest procedure, so they are not visible in the developer console and cannot be blocked by plugins such as AdBlockPlus or Ghostery. This makes these types of requests available for online tracking, de-anonymize and trace users behind common privacy protection services such as: VPN, SOCKS Proxy, HTTP Proxy and (in the past) TOR users.
Enter "about:config" in the firefox address bar and press enter. Press the button "I'll be careful, I promise!" Search for "media.peerconnection.enabled" Double click the entry, the column "Value" should now be "false" Done. Do the WebRTC leak test again. If you want to make sure every single WebRTC related setting is really disabled change these settings: media.peerconnection.turn.disable = true media.peerconnection.use_document_iceservers = false media.peerconnection.video.enabled = false media.peerconnection.identity.timeout = 1 Now you can be 100% sure WebRTC is disabled.
BA.net/adblockvpn . . . . BA.net - AdBlock Split Speed VPN for Mobile iPhone iOS Android Save Data Usage content filter tracking profiling openvpn blinkt tunnelblick pptp malware protection business security library campus school cybercafe cipa affordable easy alternative for legacy cisco vpn umbrella webtitan barracuda fortinet sonicwall sophos untangle managed pihole vpn adblock-speed-vpn-iphone email@example.com