IP LOOKUP · Exit Check
The page sends one request to this site's GeoIP endpoint as soon as it loads: it returns your current exit IP, country or region, ISP and proxy detection results. Results are shown on this page only and can be copied in one click; if the endpoint is unavailable, the page says “Temporarily unavailable” rather than falling back to a third-party public API.
Results
Looking up your exit info…
READ THE RESULT
Each of the four fields describes one fact about the network path; together they show whether your current route is working as expected, and why some services still block you.
The exit IP is the address other networks see you as. Cross-border services, streaming platforms and AI tools check which country or region that address belongs to before deciding which version to serve and which features to unlock. Switch routes on the same device and the exit address changes right away; run the check again on this page to see the new result — no browser restart needed.
Location is determined by IP registry data, usually down to the country and sometimes to the city. Content libraries, pricing and feature availability are mostly split along this field. If the region shown doesn't match where you actually are, the request is going out through an exit elsewhere — exactly what you'd expect when a cross-border route is active.
The ISP field tells you whether the address belongs to a home broadband line, a mobile network or a data center. Data center ranges are treated separately by risk-control systems, so logins, sign-ups and payments are more likely to trigger extra verification. For long-term stable logins, pick a relay or dedicated line that lands on a local broadband ISP — far less hassle than changing addresses all the time.
The endpoint reports whether the address carries proxy or data center characteristics. Being flagged doesn't mean it's unusable — only that some services may ask for extra verification; conversely, not being flagged is no guarantee either. The result reflects only what's registered in public IP databases, and each service applies its own rules.
DNS CHECK
A DNS leak means your exit address has already switched to another country, but domain lookups are still being handled by your local ISP's DNS servers. The result: pages load, yet some services still treat you as local, or you get resolved to a node that's closer to you but not recognized by the service. The three steps below need no extra tools.
Start by looking up your exit IP and location on this page and copying them down. Check once before connecting and once after, then compare the two. Only a changed exit address proves the route is actually working; if the client says “Connected” but the exit hasn't changed, a split-tunneling rule is probably keeping that request local.
On Windows, run ipconfig /all and look at the DNS Servers line; on macOS, open System Settings → Network → Details → DNS; on Linux, run resolvectl status or read /etc/resolv.conf directly. If the resolver is still your local ISP's address, lookups aren't going through the route.
Run nslookup example.com or dig example.com, note the server address returned and compare it with step 2; then refresh this page once more to confirm the exit IP hasn't fallen back to local. If both match, lookups and exit are on the same side; if they don't, you have a leak to fix.
| Symptom | Likely cause | Fix |
|---|---|---|
| Exit IP has changed, but the resolver is still the local ISP | The client isn't handling DNS lookups | Turn on “DNS over route” in the client or use the route's built-in resolver, then reconnect and recheck with step 1 |
| Pages load, but some services still say the region doesn't match | The system or browser cached old lookup results | Clear the resolver cache (on Windows, ipconfig /flushdns; on macOS, sudo killall -HUP mDNSResponder), then restart the browser |
| Lookups always resolve to a nearby local node | Local DNS and the route exit aren't in the same region | Switch to a route that lands in the target region, or use the resolver provided by the route |
| Devices behave differently | Each device has different DNS settings | Go through the three steps above on each device and use the route resolver everywhere |
PRIVACY
Privacy note
Lookup requests from this page go straight from your browser to this site's same-domain endpoint, which returns the exit info to the page; nothing is stored, and there's no fallback to any third-party public IP database. For fewer local traces, open this page in a private window.
Signing up for this service requires no email address — a username and password are enough. There's no limit on simultaneous devices, coverage spans 120+ countries and 250+ routes, payment is accepted via Alipay / WeChat / USDT, and there's a 30-day no-questions-asked refund.
FAQ
Yes. The result shows where the exit address is registered, not where your device is. Once you connect, the lookup shows whichever country or region the request leaves from; disconnect and check again and it usually goes back to your local ISP's range.
It means this site's GeoIP endpoint didn't return that field this time, or the request timed out. Hit “Check Again” to retry; if there's still no result, the page keeps the fallback text — it won't pull data from a third-party public API or show estimated values.
Some browsers refuse clipboard writes on non-secure connections or when clipboard permission is denied. In that case, select the IP address manually and copy it; the address stays in the result card as plain text so you can check it character by character.
It's no guarantee. The check only reflects how the address is labeled in public IP databases; each service applies its own rules, and login frequency, device fingerprint and payment details all affect the outcome. For long-term stability, keep a fixed exit and change routes less often.