See the network exit used for this request. After connecting or switching routes, run the lookup again and compare the location with your selected route. Check your exit and DNS resolution path separately.
Current Request
Exit IP and Location
Data source: 9OVPN GeoIP API
Preparing your lookup.
Exit IP
Temporarily unavailable
Country / Region
Temporarily unavailable
ISP / Network Provider
Temporarily unavailable
Proxy detected
Temporarily unavailable
This result reflects only the request received by our API. It does not show the traffic path for every app or determine whether DNS is leaking.
What These Details Mean
Exit IP and Location
The exit IP is the public address our API sees when it receives your request. If you use a proxy and your browser traffic goes through the selected route, the result will usually show that route's exit address. With split tunneling, this page may still use your local network.
Location is based on an IP database, not your device's location. Database updates, address assignments, and provider registration details can all affect accuracy, so this shouldn't be used to determine where someone lives.
ISP and Proxy Detection
ISP identifies the network provider listed in the database. It could be an access provider, data center, or cloud service, and may not match the name of your selected route. Proxy detection is a classification returned by the API.
“Not detected” doesn't mean your traffic isn't going through a proxy, and “detected” doesn't prove that DNS is protected. If the API doesn't return this field, its status remains unknown.
DNS Leak Check
DNS translates domain names into network addresses. Browser traffic and DNS requests may take different routes, so a changed exit IP doesn't mean DNS queries are using the same route. This page's GeoIP lookup can't see which resolvers your device contacts, so it won't claim that “DNS is protected.”
Check your client settings. Review the DNS, remote resolution, or proxy resolution options in your current configuration, and confirm what they mean in the client documentation. In split-tunneling mode, also check which rules match the domain.
Check your browser and system. Review your browser's Secure DNS settings and the resolver currently used by your system. A resolver set in the browser may differ from the client's settings. Check which one takes priority before making changes.
Review DNS logs. If your client provides DNS or connection logs, check the resolution requests and matched rules while visiting the site in question. Before sharing troubleshooting details, redact subscription URLs, account information, and the domains you visited.
Test each part separately. After changing settings, reopen the target app and check your exit again. For an independent DNS leak test, use a dedicated tool that shows resolver details and compare them with your expected configuration. A resolver location that differs from your exit does not, by itself, prove a leak.
For help importing a subscription, verifying a connection, and routine maintenance, read the Complete Guide. If the issue persists, open a support ticket in the user panel and include your device platform, client status, and the steps you've tried.