The five small tests
- Your public IP: the address websites see. This is the first thing to compare before and after connecting.
- Your ISP: the company the address belongs to. On Jio or Airtel it will be the operator, on a hostel line it may be a local provider.
- IP lookup: details about any address you paste in, useful for checking what a link or a server really points to.
- DNS leak test: shows which resolver answers your name requests. If it is still your operator's after connecting, names leak outside the tunnel.
- WebRTC leak test: shows whether a browser reveals a local or real address through its call features.
A routine you can repeat in two minutes
With the tunnel off, run the public IP and ISP checks and write down both.
Connect in the client and wait for the connected state.
Repeat the IP and ISP checks: both should now describe the server you picked, for example a data centre in the Netherlands or Singapore.
Run the DNS leak test and read the resolvers listed; none should belong to your own operator.
Open the WebRTC test last and compare the address it reports with the one from the first step.
Reading the result without panic
Why two phones on one operator can show the same address is explained on the page about what your IP is. Here the rule is simpler: compare your own before and after readings, not someone else's, and do not treat a shared address as a leak.
A real concern is when the address after connecting still belongs to your operator, or when the DNS resolvers listed are the operator's. Then check that the client is connected and that the profile is enabled for the whole device, not for a single app.
What an address check cannot do
It does not rate how private you are. Sites also use cookies, logins and device details to recognise you, and a changed IP changes none of that. Our service keeps no logs, but a checker is only a mirror of what the other side receives.
Rules on tunnels and on what a network allows differ by country and change. These tools only read what your own connection already exposes.
Where the detailed pages go
Individual pages will cover what your IP is, who your ISP is, how to read an IP lookup, and how to run a DNS and a WebRTC test step by step. They sit under this section and use the same two-minute routine, with more detail for each result. Until they appear, the five tests above are enough to answer the one question that matters: is my traffic really leaving through the tunnel, or is it not.