The test found a leak. Does that mean the VPN is not working?

It is working, just not for all traffic. A leak means one specific protocol is going around the tunnel — most often IPv6 or WebRTC. Your main traffic stays protected; it is the bypass that needs fixing.

Why is there no DNS check when others have one?

A proper DNS check requires your own authoritative DNS server — otherwise the result belongs to somebody else. We are building one, and until then we say plainly that we do not have the check and point you to a specialised service.

What does the "attention" status mean?

That there was nothing to compare against. For example, the browser revealed an IPv6 address while we have no IPv6 measurement of our own. Technically that can be either a leak or perfectly normal — we will not claim either without data.

Should I disable WebRTC completely?

Not necessarily. If you use calls and conferences in the browser, WebRTC is needed. It is enough that it reveals the VPN server's address rather than yours — which is exactly what this page checks.

The check found nothing — does that mean everything is definitely fine?

It means none of the bypasses listed here are present. These are the three most common sources of leaks, but not the whole list: individual apps outside the browser can behave differently.

VPN leak test: check IP, IPv6 and WebRTC

How our server sees you

Main address Checking…

Your address is resolved on our server from a local database and is never passed to third-party services.

Time zone

checking

Comparing your device clock with the time zone of your address.

DNS

We do not have our own DNS check yet — it needs a dedicated DNS server, and we are working on it. We would rather not pass someone else's result off as ours, so for now we honestly point you to a specialised service.

Check DNS on dnsleaktest.com

What a leak is and why it happens

A VPN routes traffic through its server, and websites see that server's address instead of yours. A leak is when some requests go out directly rather than through the tunnel, and your real address becomes visible after all. The cause is almost always technical: some protocol was not redirected.

There are three classic sources. IPv6 — if the tunnel only covers IPv4 while your provider has IPv6 enabled, some connections go around it. WebRTC — the in-browser calling mechanism, which asks an outside server for your external address in order to set up a connection. And DNS — the "what address does this site have" queries that can still go to your provider's servers.

How to read the results on this page

The "How our server sees you" block shows the addresses our server received requests from: the main one, plus IPv4 and IPv6 separately. If you are using a VPN, all of them should belong to the VPN server rather than to your provider.

Then come the verdicts. "Clear" means no bypass was found. "Leak" means an address different from the connection's was revealed. "Attention" means there was nothing to compare against — for example, the browser showed an address of a protocol we have no matching measurement for. We deliberately do not turn such cases into an alarm: scaring people with uncertainty is dishonest.

What to do if a leak is found

For an IPv6 leak, the most reliable fix is enabling IPv6 support in the VPN itself, or disabling IPv6 entirely in your network adapter settings. The second option is blunt but always works. In apps with a "block traffic outside the tunnel" feature, simply turning it on is enough.

A WebRTC leak is fixed on the browser side: in Firefox with the media.peerconnection.enabled switch in about:config, in Chromium-based browsers with an extension that restricts WebRTC. Think twice before disabling WebRTC entirely: without it, calls and conferences inside the browser stop working.

Why the check runs on our own server

A leak test by its nature handles the most sensitive thing a visitor has — their real address. Sending that address to an outside service for the sake of a pretty city label would be odd for a VPN provider, so location is resolved from a local database on our server.

The WebRTC probe also goes through our own server: the browser needs an outside counterpart for it, and most testers plug in a large corporation's public server. We use ours so that a page about leaks does not become a source of one. Results are not stored anywhere.

Frequently asked questions

Want a connection with no bypasses?

MeerGuard encrypts your traffic and replaces your address — and if something goes wrong, this page will say so plainly.

Open Telegram Bot Check my IP

Leak test