Check the browser’s actual public IP first, then review your client and DNS settings.
Waiting for results. Enable JavaScript to retrieve your public IP details.
The public IP is the request source seen by this site’s interface, not your device’s local network address. Geolocation comes from an IP database and may differ from the selected route’s label; it does not indicate your device’s actual location.
Check before and after connecting to see whether the browser’s public IP changes. With split tunneling, this site and other apps may use different routes.
The ISP typically identifies the network operator or hosting provider associated with the public IP. It may not be your local broadband provider, and it may not appear as X8VPN. By itself, it does not indicate route speed or connection quality.
If the page still shows details from your previous connection, run the check again after switching routes rather than just refreshing the client’s server list.
Proxy detection is a reference classification provided by the interface, not a status indicator for your client. A detected proxy doesn’t mean the connection is faulty; no proxy detected doesn’t prove your traffic isn’t routed through one.
If the interface doesn’t return this field, this page shows “Temporarily unavailable.” It won’t infer a result from your ISP, location, or IP address.
DNS translates domain names into network addresses. Even when web requests go through a proxy, DNS lookups may take a different route. A public IP check can’t reveal the full DNS request path, so this page won’t automatically report whether a leak has or hasn’t occurred.
After connecting to a route, review your client’s DNS, remote DNS resolution, and split-tunneling settings to confirm that proxied traffic uses the expected resolution method. Options vary by client, so consult its documentation rather than applying DNS addresses from an unknown source.
Secure DNS in your browser, encrypted DNS in your operating system, and other networking tools can all affect DNS routing. Note your current settings, then check for conflicts with your client configuration. Encrypted DNS describes how DNS queries are transmitted; by itself, it doesn’t prove they use the selected route.
Use your client’s DNS or connection logs to check how requests are handled after visiting the target domain. If you use a reputable DNS test tool separately, compare the DNS provider it reports with your actual settings. A DNS server’s location alone isn’t enough to conclude that a leak has occurred.
Change one setting at a time, then reconnect and test again. Browsers, operating systems, and apps may cache DNS results; clear the cache if needed by following your system’s instructions. When finished, restore settings compatible with your current client, and avoid running conflicting networking tools at the same time.
If you can connect but websites won’t load, or a specific app is inaccessible, see Troubleshooting. For further help, open a support ticket in the dashboard and include your device platform, selected route, and the symptoms.
No lookup data is logged. This check requests data only from this site’s GeoIP interface; results are shown on the current page and aren’t saved to browser storage. Copying is initiated by the user. This page does not use third-party public lookup services as a fallback.
Before sharing a screenshot or submitting a support ticket, obscure any public IP addresses, account details, and subscription links that don’t need to be visible. See our Privacy Policy for details on how we handle privacy.