The page reads your current exit address as soon as it loads, and shows country/region, ISP and proxy detection alongside it. Connect to an acceleration route and refresh once to confirm traffic is really leaving through that route.
Current exit
Awaiting check
Exit IP
Temporarily unavailable
Results come from this site's own same-origin endpoint and are used for this view only; refreshing the page runs a new lookup.
The endpoint didn't return a result — the connection may have dropped or the route may be switching. Tap “Check again” to retry, or work through the steps below to check your exit and DNS one by one.
Each of the four fields answers one question: where traffic leaves from, which region it lands in, who carries it, and whether the exit looks like a data-center address.
This is the source address the sites you visit see. Connect to a route and refresh this page — the address should change to an exit in that route's region. If it stays the same, traffic isn't going through the acceleration route; check the connection status in your client first.
Location is inferred from IP block databases: country level is usually reliable, city level can be off — the same block may be labelled with neighbouring cities in different databases. Judge by country, not city.
This field shows who carries the exit. Data-center routes usually show a hosting or cloud provider name, while residential broadband shows the local carrier. Both work; the difference is the landing scenario and how accepting a given site is of that source.
Some sites use this flag to judge where a visit comes from. Acceleration routes usually exit from data-center addresses, so a proxy flag is normal; what actually affects your experience is route quality and the target site's own policy, not the flag.
A new exit doesn't mean DNS resolution takes the same route. If lookups are still handled by your local network, the records stay local, and some sites will send you back to your original region based on where the resolver sits.
After connecting, refresh this page: Country / Region should match the route's location. If the exit hasn't changed, the DNS checks below won't tell you much — go back to your client, look at the connection status and routing rules, and confirm traffic is really going through the tunnel.
On Windows run ipconfig /all, on macOS scutil --dns, on Linux resolvectl status. Look at the DNS server addresses in the output: if they're still your local carrier's or router's, resolution is still happening locally.
Resolve a common domain on the same device and see which region the returned address belongs to. If the exit is in Tokyo but the resolved address sits locally, DNS isn't following the route; if the regions match, resolution is going out with the route.
First turn on the option in your client that sends DNS through the route, or switch to the resolver the route provides. Reconnect, then repeat steps 2 and 3 to confirm. Some clients only apply the change after restarting their network service, so don't jump to conclusions right away.
| Platform | How to check | What good looks like |
|---|---|---|
| Windows | ipconfig /all | DNS servers are route-side addresses |
| macOS | scutil --dns | No local carrier addresses in the resolver list |
| Linux | resolvectl status | The current connection's DNS points to the route side |
| Android / iOS | System Settings → Current Network → DNS | Leave blank for automatic, or enter a route-side address |
In global mode, DNS should follow the route entirely; in split mode, domains set to direct in your rules are still resolved locally, which is expected. Confirm which mode you're in before comparing results.
The location lookup on this page is handled by this site's own same-origin endpoint. Requests are used only to generate the current result — nothing is written to your account and no sign-in is required. The tool keeps no history and runs a fresh lookup on every refresh; if you want a record, use the copy button to take the result into your own notes.
Location data comes from IP block databases and is an inference, not an account or identity credential.
The route list shows the city of the entry or exit data center, while location is inferred from IP blocks, so the two can land in neighbouring cities. Judge whether a route is active by country; a city difference doesn't affect use.
A region usually has several exit addresses, and the client reassigns one on each reconnect. As long as Country / Region stays the same, it doesn't affect use; if you need a fixed address (for an allowlist, for example), go by the exit your client currently shows.
Some sites take the flag into account, but mainstream streaming services and work systems care more about route quality and region match. If one site keeps refusing access, try another route in the same region rather than fixating on the flag.
No. Location is a database inference and the exit address changes on reconnect, so both are only good for a one-off self-check. For account issues, submit a ticket with the time and route name.