The address target sites see
After you connect to an accelerated route, the exit IP becomes the address of that route's data center; disconnect and it returns to your local network address. This is the most direct sign that a route is working.
Network check
My IP and exit location
Look up your current exit IP, location and ISP, then compare results before and after connecting to check for DNS leaks. Lookups run on this site's servers and results are shown only for that request.
- Lookups run on this site's servers
- No third-party IP APIs
- Lookup content is never logged
Current exit details
Server-side lookup
- Exit IP
- Checking…
- Country / Region
- Checking…
- ISP
- Checking…
- Proxy detection
- Checking…
Looking up your current exit details…
Location comes from the registered details of the IP block and may differ from where the device actually is. When no result is available, the page says so instead of guessing.
Reading the results
What these results mean
Each of the four results has a purpose: the first two show whether the route is in effect, the last two show where target sites think you are visiting from.
What services use to decide your region
Location comes from the registered details of the IP block, and some services use it to decide which version of content to show. The registered location and the device's actual location can differ — common with mobile networks and data-center routes.
Judging the exit type
The organization the IP block is registered to. Home broadband, mobile networks and data centers read differently here, which helps identify what kind of exit you are on.
Flags in public IP databases
Shows whether the address is flagged as a proxy or data-center exit in public IP databases. Data-center routes are often flagged; this does not affect the connection itself, but it can affect how some sites determine your region.
Self-check steps
DNS leak check
No extra tools needed: look up your exit before and after connecting, then check the DNS settings in your client to see whether resolution follows the route.
DNS lookups decide who resolves domain names for you. If DNS requests still go out through your local ISP after you connect to an accelerated route, the domains you visit are visible on the local network — this is what's usually called a DNS leak.
An exit IP that changes while DNS stays the same is the most common form of this problem. Work through the four steps below in order and you can usually pin down which link is at fault.
- Before connecting, run a lookup and note the exit IP and location as a baseline.
- Connect to a route in the target region, confirm the client shows connected, then run the lookup again.
- Compare the two exit IPs: if the region matches the route you chose, the exit has switched.
- Check the DNS servers in your client or system network settings: they should match the exit region, not your local ISP.
| Item | Expected | Needs checking |
|---|---|---|
| Exit IP region | Matches the chosen route | Same as before connecting |
| DNS resolution region | Matches the exit region | Still points to the local ISP |
| Target site page | Shows content for that region | Says the region is unavailable |
Privacy and notes
Logging and common questions
This site does not log lookup content. Requests are used only to return the result, are not written to access logs and are not linked to an account. The page does not keep the previous result; reloading fetches it again.
The result doesn't match my actual location — is that an error?
No. Location comes from the registered details of the IP block, and the registered location can differ from where it is actually used — common with mobile networks, corporate exits and accelerated routes. To tell whether a route is working, compare the exit IP before and after connecting.
Proxy detection flags my IP — does that affect usage?
The flag means the IP block is classified as proxy or data-center use in public IP databases, which is common for data-center routes. It doesn't affect the connection itself, but some streaming sites restrict access based on it; whether a site works still comes down to opening it.
Does the lookup record my IP?
No. The lookup is used only to return the result, is not written to access logs and is not linked to an account; the page itself does not store results and fetches them again on reload.
What if the result doesn't change after switching routes?
Disconnect in the client and reconnect, confirm the status shows connected, then click “Check again”. If the exit still hasn't changed, check whether the client is in global or rule mode, whether another proxy app is running at the same time, and whether the browser is showing a cached page.
Need an exit in a specific region? See plans, or browse the route list first.