Open this page to see the IP address your network presents to the outside world, along with its country and ISP, and whether that address is flagged as a proxy or data center. Below you will find a DNS leak self-check and an explanation of all four results.
Current IP details
Data comes from the site's own same-domain lookup API and returns in a single request.
Results are not available right now. Try again in a moment, or make sure your current network can reach the site's API. After switching servers in your client, you can also click Check again.
Results are shown for this view only — the page never polls automatically. After switching servers or changing your routing rules, click Check again to see the new IP details.
Each of the four results covers a different part of the connection; only together do they show whether your traffic is really going through an international route.
Your IP address is what an outside service sees when your device connects to it. An overseas address means your traffic is already going through an international route; a local address means it is still leaving from your local network. Checking is simple: run a lookup before and after connecting, and compare the results.
Location is determined by IP databases, and it drives the region checks used by streaming and AI services. When the location differs from the one your account normally uses, some services ask for extra verification steps. This line also confirms whether the server you picked actually exits in the region you expect.
This line shows who owns the IP. A data center or cloud provider name means the address comes from a data center route — a common feature of cross-border acceleration exits. A residential broadband provider name means you are exiting through a home network. The two behave differently with streaming and AI tools.
Some services read this flag when deciding whether to let you in. Being flagged as a proxy or data center address does not mean it is unusable, but AI tools and some streaming platforms tighten their policies based on it. If you see a 'not available in your region' message, check this line first, then decide whether to switch route types.
Start in your client and confirm the routing rules are actually capturing browser traffic, then work through it step by step: IP address first, app checks second. For the full order, see VPN Connected but Not Working? A Beginner's Guide to Checking Your IP and DNS.
An overseas IP address does not mean DNS resolution happens overseas too. If your local ISP still handles DNS queries, you end up with an overseas IP but local resolution — a combination that makes some AI tools and streaming services tighten their policies.
nslookup example.com; on macOS and Linux use dig example.com. The address shown on the 'Server' or 'SERVER' line of the output is the resolver currently in use.First, a browser's built-in encrypted DNS can bypass your client settings — turn it off in the browser before testing. Second, some systems reset their DNS configuration after a network change, so re-check once after switching Wi-Fi networks or restarting your network adapter.
Confirm the IP address has changed first, then look at where the resolver sits. If the IP has not changed, digging further into DNS rarely helps — the problem is that your client is not capturing traffic, not the resolution step.
Lookup requests go through the site's own same-domain API and return instantly. Results are not written to access logs and are never linked to your account or subscription. They live only in the current browser session, so refreshing the page runs a new lookup.
IP location is public network information — any website can see the IP address a visitor connects from. This page simply shows that information back to you, so you can compare before and after switching servers.
Your client shows the entry address of the server you picked, while an outside service sees the exit address of that route — the two can legitimately differ. Trust the result on this page: if it shows a local address, your browser traffic is not going through the route.
Not necessarily. Common causes are routing rules that never captured the browser, a system proxy that did not take effect, or a client mode that only proxies selected apps. Work through it in order — IP address first, then app-by-app checks — to see which traffic uses the route before you adjust the rules.
The flag only reflects how an IP database classifies the address; it does not mean a service will refuse you. What you actually get depends on each service's policy: AI tools and some streaming platforms are more sensitive to data center addresses. If you see an unavailable message, trying a different route type is usually faster than reconnecting over and over.
Lookup requests return instantly, and results are not written to access logs or linked to your account or subscription. What you see exists only on the current page; refreshing runs a new lookup.
The page never polls on its own. Just run a lookup manually after switching servers, changing routing rules, or joining a different network — that way what you see is always the route in effect right now.