HelloVPN

DNS and WebRTC Leaks Explained, and How to Fix Them

Updated 5 min read

A leak happens when some of your traffic goes around the VPN instead of through it. The three common types are DNS leaks, which can show your internet provider which sites you look up, WebRTC leaks, which can reveal your real IP address to a website, and IPv6 leaks, where part of your traffic skips the tunnel. You can check for all three in a minute with free online tests, and most are fixed by app or browser settings.

What is DNS?

DNS (Domain Name System) is the internet's address book. When you type a site name such as example.com, your device first asks a DNS server for the matching IP address, and only then connects. By default, those questions go to your internet provider's DNS servers, so the provider can see a list of every site name you look up.

A VPN should send these DNS questions through its encrypted tunnel to a DNS server it controls or trusts. Then your provider sees only encrypted traffic going to the VPN server. If you are new to IP addresses, start with What is an IP address?.

What is a DNS leak?

A DNS leak is when your DNS questions keep going to your internet provider (or another outside server) even though the VPN is connected. Your web pages still travel through the tunnel, but the list of sites you visit is visible outside it.

Common causes:

  • A DNS server set manually in your device or router settings that overrides the VPN's.
  • An operating system feature that sends DNS queries over every network interface at once.
  • An older or misconfigured VPN app that does not handle DNS at all.
  • Browsers with their own "secure DNS" setting pointed at a fixed provider.

A DNS leak does not show your traffic content, but it does reveal your browsing pattern to whoever runs that DNS server.

What is WebRTC and how can it reveal your IP?

WebRTC (Web Real-Time Communication) is a browser technology for voice calls, video calls and file sharing directly in a web page, without a plugin. To connect two people directly, the browser has to discover its own network addresses, and a web page can ask for them with a few lines of JavaScript.

On a correctly working VPN, the address found should be the VPN server's. A WebRTC leak happens when the browser instead reports your real public IP address, which usually means some traffic is not going through the tunnel. This is more common with browser-only VPN extensions and proxies than with apps that route the whole device. Modern browsers hide your local network address by default, so the main concern today is the public IP.

What is an IPv6 leak?

Most networks now use two kinds of IP address: the older IPv4 and the newer IPv6. Some VPNs only tunnel IPv4. If your network also supports IPv6, websites that are reachable over IPv6 may be contacted directly, outside the tunnel, showing your real IPv6 address. A good VPN app either tunnels IPv6 traffic or blocks it while connected.

How do I test for leaks?

Run the tests with the VPN off first, note your results, then connect and run them again.

  1. Open VPN check to see the IP address and location websites see.
  2. Run the DNS leak test. With the VPN on, the DNS servers listed should not belong to your own internet provider.
  3. Run the WebRTC leak test. With the VPN on, your real public IP should not appear anywhere in the results.
  4. Look at whether an IPv6 address appears in the results. If it matches the one you saw with the VPN off, you have an IPv6 leak.

Test in each browser you use, because WebRTC and DNS settings can differ between them.

How do I fix a DNS leak?

  • Let the VPN handle DNS. Remove any custom DNS you set in your device, Wi-Fi or router settings while you use the VPN, so the app's DNS is used.
  • Check your browser's secure DNS setting. Chrome, Edge, Firefox and Brave can send DNS over HTTPS to a fixed provider. That is encrypted, but it goes outside the VPN. Turn it off or set it to use your current provider while you test.
  • Reconnect after changing networks. Switching between Wi-Fi and mobile data can leave old DNS settings in place for a moment.
  • Keep the app updated. DNS handling gets fixed and improved in app updates.

How do I fix a WebRTC leak?

  • Use a full-device VPN app rather than a browser extension or proxy, so all traffic goes through the tunnel.
  • Firefox: type about:config in the address bar and set media.peerconnection.enabled to false. This turns WebRTC off, so in-browser calls on some sites will stop working.
  • Brave: in Settings, Privacy and security, set "WebRTC IP handling policy" to "Disable non-proxied UDP".
  • Chrome and Edge: there is no built-in switch; Google's official "WebRTC Network Limiter" extension restricts which addresses are shared.

On iPhone and Android, a VPN app that routes the whole device usually covers WebRTC traffic too, but it is still worth running the test once.

How do I fix an IPv6 leak?

First, update the VPN app and run the test again, since most current apps handle IPv6. If the leak stays, you can turn IPv6 off on a computer or in your home router settings while you use the VPN. On phones this is rarely possible on mobile data, so rely on an app that handles IPv6 properly.

What about leaks when the VPN disconnects?

Everything above assumes the VPN is connected. If the connection drops for a moment, for example when you move from Wi-Fi to mobile data, apps can send traffic outside the tunnel until it reconnects. A kill switch blocks traffic during that gap.

How do I check HelloVPN for leaks?

HelloVPN is a full-device VPN app for iPhone, iPad and Android, so when it is connected, traffic from your apps goes through the encrypted tunnel rather than just one browser. Settings on your device or in a browser can still create a leak, so run the DNS leak test once after you install the app and again after big system or browser updates, and keep HelloVPN updated.

Try HelloVPN Premium free for 3 days

Download the app and start your trial. Cancel any time before it ends and you won't be charged.

Download on the App StoreGet it on Google Play