The routine, in order
Before connecting, write down the public address, the city and the provider shown on a lookup page.
Connect through the client with the key from the bot.
Reload the same page. The address, city and provider should now describe the server, not your home line.
Run a DNS test and look at who owns the resolvers listed. If you see your own operator, lookups are leaving outside the tunnel.
Run a WebRTC test in the browser and see whether it prints your real local or public address.
Address and provider checks
Your public address is the one the internet attaches to the connection you are using. A lookup page also guesses a location and the name of the network from it. That guess is rough, often wrong by a few cities, and it describes the network, not you personally. Treat the city as a hint and the provider name as the more reliable line.
The server list for this service is Stockholm, Zurich, Osaka, Rotterdam and Singapore. If the test shows another country while you are connected, first compare it with the server list and repeat the test, because location lookups are sometimes inaccurate. Do not look for an Indian address: there are no servers in India.
DNS and WebRTC in a few lines
A DNS lookup turns a name into a number before a page loads. If it goes to your operator while the rest of the traffic is in the tunnel, the operator can still see the names of the sites you visit. WebRTC is a browser feature for calls that can reveal addresses through the page itself, so it needs its own test.
A clean result on one test says nothing about the others. Run all three and keep each result, because a fix for one does not repair the rest.
Common reasons for a failed check
- The client shows connected, but a per-app or split rule sends most traffic outside the tunnel.
- A browser extension or a built-in secure-DNS setting uses its own resolver.
- IPv6 traffic leaves outside the tunnel on a network that offers it.
- The connection dropped and reconnected while you were reading the page.
- A cached result: reload with a hard refresh.
Limits of a leak test
A test shows a moment, not a promise. It does not tell you what any server keeps, and it does not judge a service by itself. We say we keep no logs, but only the criteria you can run yourself, like these, are worth trusting from a page that sells a VPN. Software helped prepare this page, and our editors went through it with the service settings open. We mention both so you can weigh the text accordingly.
Pages that go deeper
- What your public address is and how to check it before and after.
- Who your internet provider is, and why a lookup names it.
- A DNS leak test with a step list.
- IP lookup for any address you want to read.
- A WebRTC leak test inside the browser.