Current exit check result
Exit IP
—
- Country / Region
- —
- ISP / Network
- —
- Proxy detection
- —
- Checked at
- —
Runs automatically when the page loads
Exit check
Exit IP and DNS leak check
When the page loads it makes one request to our own same-domain endpoint for exit information, returning IP, country/region, ISP and proxy characteristics. Results are written to this page only and discarded on refresh; if the endpoint is unavailable the fields show “Temporarily unavailable” rather than falling back to a third-party public API.
- Same-domain endpoint
- Results stay on this page
- No query logging
Reading the results
What these details mean
Each of the four fields covers one thing: the IP shows where traffic leaves from, the region shows where it lands, the ISP shows who the address block is registered to, and proxy detection shows whether it sits in a publicly listed data-centre range.
Exit IP
This is the source address that target websites see. If it differs from your home broadband IP, traffic is usually leaving through a different exit; if it is exactly the same, you are most likely still on a direct connection — check that the client is connected.
Country / Region
Inferred from IP registry records and normally matches the route's landing point. If it still shows the previous region after switching, disconnect and reconnect, then refresh this page so the client and route complete a new handshake.
ISP / Network
The network name registered to this IP block. Data-centre routes usually show a cloud provider or hosting company, while home broadband shows your local carrier. Comparing the two tells you whether traffic is really going through the route.
Proxy detection
Shows whether the IP appears on public data-centre and proxy lists. Being flagged does not mean you will be blocked, but sites with strict risk controls may ask for extra verification; switching to another route and checking again usually gives a different result.
DNS leaks
A three-step self-check
A DNS leak means traffic goes through the route while domain lookups are still handled by your local carrier. Nothing reports an error; you just see the wrong region on some sites, slow loading, or an injected notice page.
-
Connect to a route first, then come back and refresh this page
Note the exit IP and region as your baseline. Without a route connected you are seeing your local exit, which makes a useful comparison.
-
Open a site that shows where your visit comes from
Regional catalogues on video sites and the region setting in search engines both reveal your source region. The region shown should match the exit region you noted in the previous step.
-
Watch for a local carrier notice or redirect
If a page like that appears, domain lookups are still going through your local DNS. Hand resolution to the route side in the client, reconnect, and check again.
| What you see | Likely cause | What to do |
|---|---|---|
| Exit region does not match the route | Still on the previous connection | Disconnect, reconnect, refresh |
| ISP shows your local carrier | Traffic is going direct | Check the client is connected |
| Proxy detection is flagged | Exit is in a data-centre range | Switch routes and check again |
| A carrier notice page appears | Lookups still use local DNS | Resolve through the route |
The table lists only the four most common combinations; when troubleshooting, compare the fields on this page with the client's connection status.
Privacy
Results stay on this page
The lookup is made by your browser and the returned fields are rendered straight into the card. They are not written to your account, not added to a support ticket, and not linked to your subscription. Once you close or refresh the page, they are gone.
To verify a route, just run the check again — no extra permission and no personal details required.
FAQ
Questions about the results
-
Why does a field show “Temporarily unavailable”?
It means our endpoint did not return usable data this time — the connection may have dropped, a browser extension may have blocked the same-domain request, or the endpoint may be under maintenance. Tap “Check again” on the card to retry; if it still fails, try a different network.
-
If the exit IP differs from your home broadband IP, does that mean traffic is already going through a route?
Usually, yes — but it could also be a shared corporate or campus network exit. Compare the client's connection status with the region shown here: only when both point to the route's landing point is the tunnel really up.
-
What happens if proxy detection reports “proxy characteristics detected”?
Some streaming, payment and high-risk-control sites are more sensitive to data-centre IP ranges and may ask for extra verification or restrict part of their content. Switching to another route and checking again usually gives a different result.
-
Does this page store the IP it looks up?
No. The returned fields are rendered straight into the card and are gone once you refresh or close the page; they are not linked to your account.
-
How long after switching routes should I refresh?
Refresh this page once you have disconnected, reconnected and the client shows a live connection. If the region is still the old one, first check that no domain-based split-tunnelling rule is sending traffic direct.