NETWORK / IP LOOKUP
See the IP address and location visible to websites during this visit. Results come from the VPNPH lookup endpoint and reflect the current request’s public IP—not your device’s full network configuration.
CURRENT CONNECTION
Getting results from the VPNPH lookup endpoint…
READ THE RESULT
This is the source address seen by the VPNPH lookup endpoint. After enabling an international route, check again to see whether traffic is leaving through the expected IP. A changed IP alone doesn’t show whether every app follows the same routing rules.
The country or region and ISP are based on IP registration data and can help identify the approximate location associated with your current public IP. This data may change as addresses are reassigned, so it doesn’t prove your device’s location or the quality of a route.
This field shows the endpoint’s assessment of your current public IP; it doesn’t check every connection on your device. If the endpoint doesn’t return a proxy field, the page will say the result is temporarily unavailable rather than draw a conclusion.
DNS CHECK
Checking your public IP and checking DNS resolution are different tests. This page doesn’t read your device’s DNS requests or present an IP lookup as a DNS test report.
Enable the route you plan to use, then return to the lookup above and note the public IP and location. If you use per-site routing rules, first confirm which route applies to the site you’re using for the check.
Review your system network settings and your browser’s Secure DNS settings. Browsers may use separate DNS settings, so checking your system settings alone may not cover browser requests.
Use your device’s network diagnostics to identify the DNS server handling your lookup, then compare it with your intended route and DNS settings. If DNS traffic is taking an unexpected path, review your client routing rules and system and browser DNS settings. A DNS server’s registered location alone isn’t enough to confirm a leak.