The page sends one request on load and shows your current exit IP, country, ISP and proxy detection. If the API returns nothing you get a clear message — no estimated values are substituted.
The result reflects your current exit only and changes once you reconnect to another route. Refresh the page to run the lookup again.
Each of the four fields answers one question: where the request leaves from, which region it is registered to, who provides the access, and whether it is flagged as a proxy source. Read together, they are more useful than the IP alone.
The address your request lands on at the other end after it leaves the route. This is what websites, apps and streaming services see; the local address in your router admin page is a different thing. Reconnect to another route and this value changes with it.
The location registered for the address in IP geolocation databases. Some services use it to decide content libraries, availability and billing currency. These databases update with a delay, so a few addresses show a neighbouring region or city.
The network the address belongs to. Data-centre ranges differ from residential ranges in that more platforms flag the former as data-centre addresses and apply stricter risk controls; residential ranges are treated more leniently, though they are not the only factor.
Compares the current address against public proxy, data-centre and VPN ranges. A match only means the address is identified as a data-centre or proxy source — not that the route is unusable. What it affects is how strict risk controls are on some platforms.
| Field | Meaning | What to watch for |
|---|---|---|
| Exit IP | Address after the request leaves the route | Differing from the address your local network sees is normal |
| Country / region | Location registered in IP geolocation databases | Updates lag, so a neighbouring region may show |
| ISP | Network the address belongs to | Data-centre ranges are more likely to be flagged |
| Proxy detection | Result of the comparison with public proxy and data-centre ranges | A match does not mean unusable; it affects risk scoring |
DNS resolution decides who can see your domain requests. If resolution still goes to your local carrier after you connect, you end up with an exit abroad and local resolution — and some sites read that combination as an inconsistent connection.
System-level DNS on iOS and Android overrides client settings. After changing it, trust the resolver shown in the system settings rather than the client toggle alone.
| Symptom | Common cause | What to do first |
|---|---|---|
| Resolver is local, exit is abroad | Client DNS is not following the route | Set it to “follow the route”, reconnect and test again |
| Resolution and exit in the same country, different cities | Resolver node and exit server sit in different locations | Usually nothing to fix if playback and sign-in work |
| Some domains fail to resolve | The local network blocks plaintext resolution | Switch to another route, or use route-side resolution |
| The same domain returns different results each time | Several resolvers are being rotated | Normal; judge by the region |
Lookups are instant and the result only serves this screen. The five points below describe the data flow.
The four places people get stuck most often all point to the same actions: reconnect, look up again, compare.
If the exit looks right but the target service still will not load, it is usually the route type or the resolution settings. Work through the order below.