Run a lookup before and after you connect, then compare the public IP, country/region and ISP. If DNS requests are not following the route, work through the DNS leak test steps below.
Looking up your public IP…
Data comes from this site's same-domain GeoIP endpoint; the location is based on IP database results and city-level accuracy is limited. Run the lookup again after switching routes or reconnecting.
Each of the four fields answers a different question. Reading one on its own is easy to misjudge; together they tell the real story.
The source address that destination websites see. Once you connect to an accelerated route it differs from the address your local broadband assigns; after you disconnect it should return to the original value — if it doesn't, proxy settings are still left on the system.
The registered location of the public IP, which usually decides streaming regions and which services are available. City-level results come from IP databases and are limited in accuracy — different data centers in the same city may show different names.
The carrier or data center that owns the IP range. Showing a data center is normal — accelerated routes run in data centers, not on residential broadband. What matters in this field is that it differs from your local carrier.
A risk flag that IP databases assign based on historical behavior. A flag doesn't mean the IP is unusable, but some platforms will ask for extra verification. If you keep hitting CAPTCHAs during everyday browsing, switch to another route and check again.
DNS resolution decides who handles the step of matching a domain name to an IP address. If your system hands those requests to your local carrier, the results can still reveal your real region even when web traffic goes through an accelerated route, and some services will serve content based on your local region.
nslookup example.com; on macOS and Linux use dig example.com +short or nslookup example.com.This page only shows the location data of your public IP and does not read the DNS configuration on your device. The command in step 3 has to be run locally, and output field names differ slightly between systems.
Your public IP is publicly queryable information — any website you visit can see it. This page just shows it in one place so you can compare the state before and after connecting.
Lookups are used for that display only: results are not written to account data and are not tied to a username. Requests from this page go only to this site's same-domain endpoint.