Simply put, WebRTC (Web Real-Time Communication) is an open-source project that provides most browsers with a feature that allows voice, video chat, and P2P sharing to occur without any additional extensions or add-ons being used.
WebRTC is usually pretty useful, but it can be detrimental to your online privacy if you are using a VPN and experience a WebRTC leak.
A WebRTC leak is a vulnerability that leaks your real IP address when using a VPN. How does WebRTC know your IP address? Well, it uses the ICE (Interactive Connectivity Establishment) protocol to discover it, and it also uses STUN/TURN servers which can actually see your IP address just like websites can.
Basically, here’s what the problem is:
Even worse, the requests are made outside the normal XMLHttpRequest process – an API that transfers data between a web browser and a web server. Because of that, the requests can’t be seen in the developer console. Also, they can’t be blocked with plugins like Ghostery or AdBlockPlus.
It’s important to understand that a WebRTC leak isn’t an issue with the VPN service itself, but with the web browser you’re using.
The answer is pretty simple – if your IP address is leaked while connected to a VPN service, that makes it much easier for the government to spy on you, your ISP to track your activities, and cybercriminals to exploit your sensitive data. Not to mention it completely defeats the purpose of using a VPN in the first place.
And lastly, since the STUN requests can’t be seen in the developer console or blocked with various plugins, they can be easily tracked online by advertisers if they set up and configure their own STUN server that uses a wildcard domain (also called a wildcard DNS record).
The process is relatively simple – just do the following:
You might also notice that – sometimes – test results show your internal/local IP address too (usually in the following format – 10.x.x.x. And 192.x.x.x.). We recommend not worrying about that since the only thing that matters when trying to detect a WebRTC leak is the public IP address.
If you’d like to try out other tests that cover WebRTC leaks, here are some options:
Also, if you’d like to learn about other ways to test VPN connections, here’s an in-depth guide we wrote on the topic.
Here are three things you can do to solve this problem:
If you use Firefox, you’ll be happy to know you can directly disable WebRTC in it with ease.
Here’s what you need to do:
If you are a CactusVPN customer, you can use our Firefox extension to easily disable WebRTC.
If you have Chrome on mobile, you can disable WebRTC manually on it too. Just type in or copy the following URL in a Chrome tab:
Once the page is loaded, just scroll down, look for “WebRTC STUN origin header,” and disable it. While not necessary, you can also disable the “WebRTC hardware video encoding” and “WebRTC hardware video decoding” options if you want to be extra safe.
The Brave browser is also susceptible to WebRTC leaks since it’s based on Chromium. The easiest way to fix the problem is to do the following:
If that doesn’t work for you or you want to try something else, an alternative way to stop WebRTC leaks on Brave is to go to “Preferences>Security>WebRTC IP Handling Policy” and just select “Disable Non-Proxied UDP.”
In the case of browsers where WebRTC can’t be disabled, you need to use third-party browser add-ons and extensions to solve the problem. Here’s a quick overview of your options:
One thing we really need to emphasize is that add-ons and extensions aren’t always 100% fool-proof. There’s always a very small chance that you might still be exposed to a WebRTC leak when using them, so keep that in mind.
Of course, you could always just stop using the browsers that don’t let you disable WebRTC directly altogether. If you really need to use one, though, we’d recommend picking Opera over Chrome.
Even though the WebRTC leak issue is a problem you mostly need to worry about if you use a VPN service, you can solve and prevent it with a different VPN service – as long as the provider can guarantee they offer complete WebRTC leak protection. In this case, it really helps if they offer a free trial so that you have time to thoroughly test the connections to make sure no leaks occur.
As a general rule of thumb, free VPN services should be avoided if you want to make sure you get the WebRTC leak protection you want.
We’ve got you covered – we ran multiple tests on CactusVPN connections while using the solutions mentioned above to make sure they don’t experience any WebRTC leaks.
Plus, that’s not the only way we protect your privacy. We also use high-end encryption (AES), we don’t log any of your data, we offer DNS leak protection, and we provide access to six VPN protocols: OpenVPN, SoftEther, SSTP, IKEv2/IPSec, L2TP/IPSec, PPTP.
We offer user-friendly VPN apps you can quickly install on various platforms: Windows, macOS, iOS, Android, Android TV, Amazon Fire TV.
We provide a free trial, so you have plenty of time to see if our VPN services can meet all your needs. Plus, there’s also enough time to test our connections a lot too.
What’s more, once you become a CactusVPN user, we’ll also have your back with a 30-day money-back guarantee if there are any problems with our service.
A WebRTC leak is a vulnerability that can occur in multiple web browsers (Firefox, Google Chrome, Brave, Opera) which can leak your real IP address when you are connected to a VPN service.
Luckily, it’s pretty easy to detect WebRTC leaks, and you can quickly fix the problem on all browsers. Choosing a VPN service that offers WebRTC leak protection helps as well.
Protect online privacy, secure your connection and access blocked websitesTry CactusVPN For Free