IP Check
Once you're connected through a route, open this page to see the exit IP, country and ISP that target sites actually read. Lookups go through our own same-domain endpoint and results stay on this page; below you'll find what counts as a DNS leak and how to check for one step by step.
The lookup starts automatically once the page loads; if nothing appears after a while, tap “Check again.”
Field guide
The four fields answer different questions: which region a site places you in, who the address is registered to, and how risk systems read it.
Once you connect through a route, this is the address target sites see instead of the public IP your local broadband assigned. It decides which language version you get, which regional content library and pricing you see, and it's the first thing login risk checks read. The exit address changes with the route, so it's worth checking again every time you switch.
Location comes from the IP address registration records, which regional internet registries allocate block by block to ISPs or data centers. It doesn't always match the route name: a relay route's exit can land in the country or region where the landing data center sits. Go by what this page shows; if it's far from what you expect, switch to another route in that region and test again.
This field shows who the address block is registered to — usually an ISP name, a data center name or an autonomous system number. Residential broadband addresses and data-center addresses score differently with many sites' risk systems: the former look more like ordinary visitors, while the latter are often asked for extra verification. It's reference information only and doesn't affect whether the route itself connects.
Some sites compare against public lists of data-center address blocks to judge whether a visitor is coming in through a proxy. A proxy hit doesn't mean the route is unusable — most sites are unaffected; a few may ask for a CAPTCHA or a second confirmation, and switching to another route usually gets around that.
Connection integrity
A healthy exit address doesn't mean domain lookups also go through the route. DNS leaks are a common reason an IP looks fine while pages still treat you as local.
Before your device can reach a domain, it has to resolve that domain to an IP address. If the lookup doesn't go through the route and instead goes straight to your local ISP's DNS servers, then even when page traffic travels through the route, the lookup records still reveal your approximate location and ISP. That's what a DNS leak is.
| Check | Normal | Needs attention |
|---|---|---|
| Exit IP location | Matches the route's region | Switch to another route in that region and check again |
| DNS resolver location | Matches the route's region | Turn on DNS over route in the client, or use route-side DNS |
| Exit address before vs. after connecting | Differs after connecting | Make sure the client shows connected; reconnect if needed |
This page can only verify the exit IP; resolver location has to be confirmed in the client or at the system level.
Data notes
The lookup happens only between you and our own endpoint, with no external service involved.
Location lookups are handled by our own same-domain endpoint, only for the exit address of the current request, and only to display on this page.
Results aren't written into your account profile and aren't linked to orders, subscriptions or tickets; refreshing the page runs a new lookup.
On connection logs, our policy is not to keep them; the full scope and exceptions are set out in the privacy policy.
Subscriptions don't require an email address — a username and password are enough, and your account holds no extra personal details.
See the Privacy Policy for the full terms, and VPN security guide for beginners for how to look after your subscription link.
FAQ
For more connection and billing questions, see the Help Center.