Free IP tools and security checks

What each check tells you

• IP check: the public address a site sees. If it does not change when you switch the service on, nothing is being routed through it.
• DNS check: the resolver that looks up site names. With a plain proxy this is often still your own network's resolver.
• WebRTC check: whether the browser exposes addresses on its own, outside the proxy setting.
• Local address and ISP lookups: useful for context, but they only describe the network you are on, not what leaves it.

Why a proxy fails these checks more often

A proxy handles requests from the apps you point at it. Anything the app does outside that path, such as a DNS question or a direct browser connection, may travel the ordinary way. A full tunnel takes the whole connection on the device, so fewer things slip around it. Our client side works as a VLESS subscription, and a client in TUN or system-wide mode is what moves the whole device onto it; in plain proxy mode only the apps that follow the proxy setting go through it.

That is why the tests matter more for proxies than for tunnels, and why a green result in one browser tab proves nothing about a game or a messenger on the same phone.

A ten-minute routine

1. 1

   Open any IP lookup page on your normal connection and note the address and provider shown.

2. 2

   Turn the service on, reload, and compare. A different address in one of our server countries (Germany, Austria, Czechia, Singapore or South Korea) is what you should see.

3. 3

   Do a DNS leak test, then look at the resolver names it lists. If they still name your home provider, your DNS questions are going around the service.

4. 4

   Run a WebRTC test in the browser you actually use, not in a clean one.

5. 5

   Repeat after changing network, for example from home Wi-Fi to mobile data, because settings sometimes apply to only one of them.

Public Wi-Fi and college or office networks

Shared networks add a second question: who runs the network and what can it see? On café, hotel, college or office Wi-Fi the owner of the network can usually see which addresses you connect to and the unencrypted parts of your traffic. HTTPS content stays encrypted between you and the site, with or without a tunnel. A tunnel hides the destinations from the network owner and shows them to the tunnel operator instead, so you are choosing whom to trust, not removing trust.

Networks may also have their own rules about VPNs and proxies. Rules differ by country and by network and they change, so the duty to follow local law and each network's own terms is yours; this page cannot decide it for you.

Where the tests stop

No browser test can prove that a service keeps no records, only what it shows to the outside. Our stated position is that no log is kept of your visits or connections; a leak test can neither confirm nor refute that. It confirms the routing, nothing more.

Selling a VPN is our business, which is why the routine above is built to test us as much as anyone. An AI model produced the first version of this page, and an editor revised it against the service's facts. If a test fails, fix the setup or stop relying on it; do not shrug the failure off as a quirk.

Separate pages follow for each test: your public address and what a proxy changes, who your ISP is, the DNS leak test, IP lookups, WebRTC, and the Jio, Airtel, Vi and Bsnl questions.

Before you trust a green result

• Test on the same device and in the same app you use daily.
• Test on mobile data and on Wi-Fi separately.
• Re-run after updating the client or the browser.
• Note the time; some results depend on whether a connection was refreshed.
• Treat one passing test as one fact, not a verdict.