Same-Origin GeoIP Lookup
This page reads the public IP address used by the current web request and displays the returned country or region, ISP, and proxy status. Run the check before and after connecting to compare whether your public IP has changed.
The check starts automatically when the page opens. Results come from this site’s same-origin GeoIP endpoint; no preset values are used.
Getting current public IP details
GeoIP results are useful for verifying changes to your public IP, but a geolocation database entry is not the same as your actual physical location. Review the selected route and access performance together when checking connection status.
This is the network address the current web request presents to the internet. Run the check before and after connecting to 14VPN; a changed address indicates that web traffic is using a different public IP. Other browser tabs may retain older connections, so refresh the target page when verifying.
Location data comes from a GeoIP database and shows the region registered for this address. Data-center moves, address-range reassignment, or database update timing can cause differences from the route name, so use this information as a location clue rather than a definitive result.
This field identifies the network organization associated with the public IP. Before connecting, it usually shows your local access network; afterward, it may show the data center or network operator used by the route endpoint. If the endpoint returns no value, the page will clearly say that it is temporarily unavailable.
This field only reports how the GeoIP endpoint classifies the current address. It does not indicate connection quality and cannot, by itself, determine your privacy status. Databases may classify data-center addresses differently, so first verify whether the public IP matches the selected route.
DNS Resolution Check
This page’s GeoIP check can only see the public IP used to access the site; it cannot directly list the DNS resolvers used by your device. To check for DNS leaks, compare the public IP location with the resolver information shown in your system or browser network diagnostics.
Keep the target route connected, wait for the check above to finish, and record the public IP and country or region. If the check fails, do not use that result to determine whether a leak exists; run it again after the connection is restored.
Open your operating system’s or browser’s built-in network diagnostics and find the DNS resolver currently in use. Menu names vary by system; check network settings, connection details, or Secure DNS settings.
If the resolver consistently points to a local network clearly unrelated to the selected route, check your system DNS, browser Secure DNS, and client split-routing settings. A regional mismatch is only a troubleshooting clue, not proof of a leak.
After switching routes or reconnecting, refresh this page and review the network diagnostics again. If the issue persists, open the DNS issues section in the troubleshooting guide, or sign in to the user panel to submit a ticket.
The request is sent to 14VPN’s same-origin GeoIP endpoint, and 14VPN does not log the result. Failed requests are not forwarded to a public third-party service, and sample addresses are never used in place of real results.
The copy button copies only the public IP currently displayed. If the browser denies clipboard access, the page will prompt you to select and copy it manually; the content is not sent elsewhere.