Your IP: 127.0.0.1 • ISP: Local • Your Status: Unprotected
Your browser is exposing IP addresses to sites that you visit.
|22.214.171.124||Public IPv4||Potential leak|
Your private information may be compromised, even if you’re using a VPN.
Public IPs are highly specific to you. They form part of your identity on the internet. When you use a VPN, sites see the VPN server’s public IP address instead of yours, and your identity is protected.
However, if WebRTC detects your real public IP address when you’re connected to a VPN, as opposed to the VPN servers, then third parties can still use it to identify you. If you see a public IP in the test results, then you may have a privacy leak.
Local IPs are not specific to you. These IPs are assigned to you by your router and are reused millions of times by routers all over the world. So if a third party knows your local IP address, it has no way of linking it directly to you. If you see a local IP in the test results, it is not a threat to your privacy.
Web Real-Time Communication (WebRTC) is a set of protocols and APIs created by Google to enable real-time voice and video communication via peer-to-peer connections.
It is a set of protocols and APIs that allow web browsers to request real-time information from other users’ browsers, allowing for real-time peer-to-peer and group communication such as voice, video, chat, file transfer, and screen sharing. WebRTC enables developers to integrate communications directly into web browser-based enterprise tools like CRM software or social apps.
WebRTC is designed in a manner that it uses highly advanced methods to discover your IP addresses which is not the way a “standard” IP detection works. With WebRTC, the ICE (Interactive Connectivity Establishment) protocol reveals your true IP address, which is then used to connect to other people via STUN/TURN servers.
This means that a third party could use WebRTC in a browser to discover your true IP address, revealing your identity.
WebRTC uses ICE (Interactive Connectivity Establishment) protocol to discover IPs. The two techniques it uses are:
STUN/TURN servers serve two important functions in WebRTC: they allow web browsers to ask, “What are my public IPs?” They also allow two devices to communicate with each other even if they are separated by NAT firewalls. The former is the one that has the potential to intrude on your privacy. STUN/TURN servers discover your IP addresses in the same way that a website does when you visit it.
Most devices have multiple IP addresses assigned to them. Firewalls are typically used to hide these from websites and STUN/TURN servers. The ICE protocol, on the other hand, specifies that browsers can obtain these IPs simply by reading them from your device.
Following browsers are vulnerable to WebRTC leaks unless you have a VPN like OysterVPN that has WebRTC leak protection:
You will experience WebRTC leaks when using these browsers but if you configure your browser properly then you can easily secure yourself from WebRTC leaks.
OysterVPN makes every effort to ensure that its apps protect you from WebRTC leaks. Your public IP addresses will not be leaked if you open new web pages while connected to OysterVPN.
WebRTC leaks are relatively a new thing in the cyber-security industry and OysterVPN knows the graveness of it. Which is why Oyster Technologies has invested in a team of dedicated resources comprising engineers and ethical hackers that keep on testing various protocols across all OysterVPN apps, ensuring that our service is safe and secure for the users.
Some other ways to prevent WebRTC leaks is by manually disabling WebRTC in your browsers.
Use “uBlock Origin” or “WebRTC Network Limiter” chrome extensions. Both of these chrome extensions have proved to protect from WebRTC leaks.
The only way to disable WebRTC in Safari is by simply not granting any particular site permission to use audio or video capture, you might expose your IPs.
To disable WebRTC in Opera, you’ll need to download the extension WebRTC Leak Prevent and follow these steps:
Unfortunately, there is no way to completely disable WebRTC in Microsoft Edge at the moment.