My IPNo sign-in · No query logs
My IP and location lookup
The page reads your current exit IP, country and carrier from this site's endpoint and returns one proxy check result. Switch to another route and open it again — the numbers should change, which is the most direct way to confirm a route is really in effect.
- Exit IP
- Fetching…
- Country / Region
- Fetching…
- ISP
- Fetching…
- Proxy check
- Fetching…
Results are unavailable right now. The endpoint returned no data — the current network may be blocking the request, or the service may be under maintenance. Try “Check again” in a moment.
While you wait, check the route status in your client: a changed exit IP is the clearest evidence that the route is now carrying your web traffic.
What these details mean
Each of the four fields answers one question: who you look like from the outside, where you appear to be, who the address is registered to, and what type of address it is judged to be. Reading them one by one beats staring at a string of digits.
Exit IP
This is the address websites and apps see. Before you connect it points to your local network's exit; once a route is up it should change to an address in that route's region. The same account showing different exits on different routes is normal.
Country / Region
This decides which regional version of a service you get: catalogues, stores and search results all key off this field. It is inferred from an address database, so it can differ from the data centre's real physical location — cross-border addresses especially.
ISP
Shows who the address is registered to. The gap between data-centre and home broadband addresses is most obvious in this field, and streaming platforms often weigh it when judging region. If you see a hosting company name, it is a data-centre route.
Proxy check
A single judgement from a database, based on address type and past behaviour; different databases disagree with each other. It reflects this lookup only, not what a target platform actually decides — a “proxy detected” flag does not mean every service will turn you away.
DNS leak self-check
A changed exit IP does not mean every request goes through the route. If domain lookups still go to your local carrier, pages will load, but the lookups and access records stay on your original exit.
- First confirm the route is connected. Open this page after connecting: if the exit IP differs from the unconnected one, web traffic is going through the route. If the number has not changed, go back to the client and confirm it is capturing traffic before worrying about resolution.
- Check the DNS address on the device. On Windows: Network & internet → Adapter options → Properties → Internet Protocol Version 4/6. On macOS: System Settings → Network → Details → DNS. On iOS and Android, look in the client's DNS or routing settings.
- Confirm the client is handling lookups. Most clients offer a DNS takeover or remote DNS switch; with it on, lookup requests travel out with the route. With it off, the device keeps using system DNS and the resolution path stays local.
- Re-check after the change. Reload this page to confirm the exit has not changed, then visit your usual sites and watch first-screen load times. Lookups taking a detour usually show up as a slower first byte, not lower bandwidth.
Lookups and privacy
Lookup requests are handled by this site's own same-domain endpoint. Results return only to the current browser; nothing is written to your account and no query history is stored.
The page works without signing in. If the endpoint is unavailable it says so directly — “temporarily unavailable” — and never hands the request to a third-party service.
These details are used only on this page: to confirm a route is active and to judge whether the resolution path needs adjusting. This service offers 110+ countries / 150+ routes — switching to another route and checking again is the most direct comparison.