Our own GeoIP API · queries never stored
Exit IP, location, ISP and proxy detection are returned instantly by our own API; when the API is unavailable the page says so plainly, with no third-party fallback.
Fetching results…
Field guide
The four fields answer four different questions: what your exit address is, where it is registered, who operates it, and whether it carries proxy traits. Knowing how to read them saves a lot of guesswork when troubleshooting a connection.
This is the source address that international sites see when you visit them. Once you connect to an accelerated route, it should show an address in the region of the route you picked; if it still shows your local carrier's address, your traffic is not going through the accelerated link — go back to the client and check the connection status and proxy mode.
The registered location of the IP block in the database, usually down to country and city. It describes where the address is registered, not where the user is; databases update at different times and label cities differently, so a neighbouring city is common.
The network operator that owns this IP block. Accelerated routes usually exit through data center networks, so seeing a data center or hosting provider name here is normal — it does not map directly to the route type (IEPL dedicated / relayed / direct).
A heuristic verdict based on the IP block's public characteristics (data center attributes, known proxy ranges and so on). It reflects this API's own assessment only — it is not the final word from the site or streaming platform you are visiting, and it does not affect whether the route works.
DNS check
A DNS leak typically looks like this: web traffic goes through the accelerated route, but domain lookups are still handled by your local carrier — some sites fail to load, or they load with a region that does not match your route. The four steps below use built-in system commands to confirm where lookups go; no extra tools needed.
Pick a route in the client and connect, come back to this page and click “Check again”, then note the exit IP and location. This is your baseline — every later check is compared against it.
Windows, macOS and Linux all ship with this command. Open a terminal (Command Prompt or PowerShell on Windows), type nslookup example.com and press Enter, then read the Server: address on the first line of the output. iOS and Android do not include it — check the resolver address shown in your client's connection details instead.
If Server shows a local carrier or private-network address (such as 192.168.x.x or 10.x.x.x), lookups are probably not going through the accelerated link; if it shows a resolver in the route's region, lookups and exit match and no leak was found.
Most clients offer switches such as “Proxy DNS” or “Remote DNS” — turn them on and reconnect. If your browser has “Secure DNS / DoH” enabled, turn it off or point it at a resolver that matches your route; otherwise the browser resolves names on its own and ignores the client settings.
Still not right after the checks? Paste the exit IP, location and ISP from “Copy results” on this page into your ticket, along with the client name, route name and OS version; those three details are enough to pin down most exit and resolver mismatches.
Tickets are opened from the Tickets page in your dashboard; you can also read the troubleshooting guide chapters on “Connected but pages will not load” and “DNS issues” first.
Privacy
Lookups on this page are used only to return a result on the spot: the API reads the IP block's registration data and sends it straight back to your browser. Queries are not written to a database and are not used for profiling.
Location data comes from static IP database records and may lag behind updates; the country, city and operator shown are for reference only and cannot be used to identify a visitor.
Our privacy policy is built on a no-logs rule. We keep no connection logs and no browsing content, and IP lookups are not archived either; results stay on this page only and are gone once you refresh or close it.
FAQ
Four common questions about location data, proxy detection and resolver settings — the checks in the answers work both in the client and on this page.
Related pages