IP Check · Exit IP & Location Lookup
Check your current exit IP, location, and ISP in one click; run the lookup again after connecting to a route to confirm it's active. Results come straight from this site's own API, with no third-party services involved.
- Country / Region
- —
- City
- —
- ISP
- —
- Proxy Detection
- —
Fetching data from this site's API…
What these details mean
Your exit IP, location, ISP, and proxy flag each answer a different question about your current connection. Compare them one by one to tell whether this session is going through your local broadband or an accelerated route.
Exit IP
When you visit international websites, the exit IP is the source address their servers see. After connecting to an accelerated route, the exit IP should change to an address in the route's region; if it still shows your local broadband IP, this session isn't going through the route—check your client's connection status.
Location & ISP
Location and ISP details come from IP databases and show whether your connection runs through local broadband or an overseas data center. Databases update at different times, so city-level labels can be off—treat the country / region field as the reliable one.
Proxy Detection
Some databases flag whether an address range belongs to a data center or is used for proxy traffic. Treat this flag as a rough hint: a "suspected" label doesn't mean the route is unusable, and "residential" doesn't mean safer—databases often disagree with each other.
Use this page to confirm your route is active
Three lookups, under a minute—no extra tools needed.
- Run a check before connecting. Note your current exit IP and ISP—usually your local broadband provider—as a baseline.
- Connect to a route. Open your client, pick a server (e.g. "Hong Kong · IEPL") and confirm the status shows connected.
- Come back and refresh this page. The exit IP should now show an address in the route's region, with the location updated to match. If the IP hasn't changed, check your client's connection status or try another server.
DNS leak self-check
DNS resolution is the most easily overlooked part of the chain, and worth checking on its own.
After you connect to a route, your browsing traffic goes through it—but if DNS queries for domain names are still handed to your local ISP, that's a DNS leak: the lookup process is exposed on the local network, and results can be steered to wrong addresses. The classic symptom: your IP shows an overseas location, yet sites load slowly or fail repeatedly.
The self-check takes two steps: first confirm on this page that your exit IP has changed to the route's region; then watch how overseas sites actually load. If the IP looks right but browsing is clearly broken, DNS is most likely still resolving through your local network.
With your client's default settings, DNS resolution is usually handled by the route as well. If you've manually changed your system DNS, switch it back to automatic so lookups don't bypass the route.