Browser Connection Details

IP Lookup and Geolocation

See where this request reaches our site from. Checking before and after connecting to a route can help determine whether your browser’s public IP has changed.

Current Connection Details

Lookup via our endpoint
Public IP
Temporarily unavailable
Country / Region
Temporarily unavailable
Internet Service Provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Enable JavaScript to check your current connection details.

Understanding the results

Your public IP is the source of this request

This is the public address seen by our endpoint, not your device’s local network address. With split-tunneling rules enabled, different websites may use different routes. A change here only reflects the route used to reach our endpoint; it doesn’t mean every app uses the same exit.

Geolocation and ISP data come from IP records

The country or region reflects how an IP address is classified in geolocation databases; it doesn’t indicate your device’s actual location. The ISP field may show a carrier, data center, or organization associated with the address. Records can be out of date. If the result doesn’t match your selected route, check the client’s exit and the destination service as well.

Proxy detection doesn’t verify your connection

The proxy field shows information supplied by the lookup endpoint. “No proxy detected” doesn’t mean you aren’t using one, and “Proxy detected” doesn’t identify the protocol. If the endpoint can’t provide a clear result, this page will show “Temporarily unavailable” rather than infer one from the IP or ISP name.

For help understanding routing modes and route types, see the setup guide. If you’re having connection issues, visit the support page.

Checking for DNS leaks

DNS translates domain names into IP addresses. A public IP lookup only shows the source of web requests; it can’t show which resolver handles your DNS queries. This page doesn’t run a DNS leak test, and a successful IP lookup doesn’t mean DNS has passed a check.

  1. Start with your client settings. Check the current routing mode, DNS interception, and resolution rules. Routing app traffic through a route doesn’t mean DNS requests take the same path.
  2. Then check your browser settings. Secure DNS in your browser may use a separate resolution path. Review it alongside your client settings; changing only one doesn’t confirm that both are aligned.
  3. Check actual DNS records. If your client provides DNS logs or connection records, review the resolver targeted by domain queries and their outbound route. A resolver’s location alone doesn’t establish a leak. First determine which route is expected.
  4. Don’t draw conclusions without evidence. If you can’t view DNS records, treat the result as unconfirmed. For help, sign in to the user dashboard and submit a support ticket with your system, client mode, and a description of the issue.

Go to support tickets. Before sharing screenshots, hide your subscription URL, account details, and any other unnecessary personal information.

Privacy and limitations

We don’t log queries. Requests are sent only to our endpoint to retrieve your current connection details. If the endpoint is unavailable, this page won’t switch to a third-party public lookup service.

The copy action copies only your public IP, not account or subscription details. A public IP may reveal information about your network location. Check what you’re sharing before posting troubleshooting screenshots.

The results on this page can’t confirm the overall privacy status of your connection or replace a DNS route check. For details on how information is handled, read our Privacy Policy.

Try it free