VPNRT · Connection Check
See where this browser request connects to the internet. Run the lookup again after connecting to a route to compare the public IP. Results don’t represent the connection paths used by every app on your device.
Enable JavaScript to look up your current connection details through a VPNRT endpoint.
Your public IP is the address the lookup endpoint sees as the source of your request. After connecting to a route, it may change to that route’s exit address. If your browser uses a direct connection, it may remain unchanged.
Country and region are estimated using IP geolocation databases, not your device’s precise location. Database updates, IP allocation, and network routing can all affect the result, so it shouldn’t be used to determine where you actually are.
ISP usually identifies the carrier or network organization associated with an IP address. It may not be your current broadband provider, and it may not match the name of your selected route.
Proxy status is a classification provided by the lookup endpoint. “No proxy detected” doesn’t mean your traffic isn’t using a proxy, and “Proxy detected” isn’t a security verdict. If the endpoint can’t provide a clear result, this page displays “Temporarily unavailable.”
For a useful comparison, use the same browser and split-tunneling rules throughout. Note your public IP before connecting, then connect to the route you want to check and run the lookup again. If the result hasn’t changed, check the client’s connection status, your browser’s proxy settings, and whether this site is set to connect directly.
For connection instructions, see the Getting Started Guide. To learn about the differences between direct connections, relays, and dedicated routes, see the Technical Reference.
DNS translates domain names into network addresses. A change in your public IP doesn’t mean DNS queries are taking the same route. This page’s IP lookup endpoint doesn’t test DNS, so it won’t report a result such as “passed” or “leak detected.”
Start by reviewing your client’s DNS and routing settings. Confirm whether DNS should be handled by your system, browser, or client. Per-app proxy settings, routing rules, and browser Secure DNS settings can send different requests along different paths.
If your client provides DNS or connection logs, check which resolver handled the test domain and which rule was applied. If logs aren’t available, review your system’s DNS configuration. A list of settings shows what’s configured, but can’t by itself prove the route a request actually took.
If you use a standalone DNS testing tool, read its privacy policy first, then compare the resolver locations before and after connecting. A resolver associated with your local ISP may warrant further investigation, but a resolver elsewhere doesn’t by itself prove there’s no leak. Base your assessment on whether actual logs match your expected routing rules.
This page doesn’t send requests to external DNS testing services. After changing your settings, reopen the website you want to check and test again. Browser and system caches may affect the comparison.
Queries aren’t logged. This page uses only VPNRT’s GeoIP endpoint to retrieve connection details for the current request. Results aren’t saved to your browser’s local storage, and third-party public endpoints aren’t used as a fallback if the lookup fails.
The copy button copies only your current public IP—not account or subscription details. An IP address can reveal information about your network, so check screenshots and diagnostic logs before sharing them. For details on other data handling, see the Privacy Policy.