Your browser’s current network

Check your public IP and DNS

First, check where this connection is exiting from, then verify whether DNS resolution behaves as expected. After switching routes, run the check again and compare the results.

Current connection details

Our endpoint only
Public IP address
Temporarily unavailable
Country / region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Waiting for results. If they don’t load automatically, try again. We won’t fall back to another lookup service.

What these results mean

These results reflect the route used by this browser request. They don’t show whether every app on your device uses the same route.

Public IP and reported location

The public IP is the address our endpoint identifies when it receives this request; it is not your device’s local network address. The country or region comes from IP geolocation data, which may be out of date and cannot establish your device’s actual location.

Check before and after connecting to see whether the address and reported location change as expected. If they don’t, make sure your client is connected, then check whether its routing rules send your browser or our site through a direct connection.

ISP and proxy detection

The ISP is the network provider reported by our endpoint. It may be an internet carrier or a hosting provider, and may not match the brand of your selected route.

Proxy detection is only the endpoint’s assessment. “No proxy detected” does not mean you aren’t using a proxy, nor does it guarantee privacy. If the endpoint can’t make a clear determination, this page shows “Temporarily unavailable” rather than treating an unknown result as a negative.

How to check for DNS leaks

Your public IP and DNS resolution are separate parts of a connection. The IP lookup on this page does not run a DNS leak test.

  1. Check your client’s DNS settings

    Once connected, check whether your client handles DNS requests according to its current configuration. Settings may have different names in different clients, so refer to the client’s documentation. Don’t assume the DNS route based only on whether the connection toggle is on.

  2. Check your browser and system DNS settings

    Secure DNS in your browser, custom DNS services, and system network settings can all affect which resolver is used. Note your original settings, then check them one at a time to make it easier to identify the cause.

  3. Verify the route using resolver details

    To confirm whether DNS is leaking, use a tool that runs an actual DNS test and lists resolver details, then compare them with your client’s DNS logs. A difference between the resolver’s location and your public IP location alone does not prove a leak; you also need to determine whether requests followed the expected route.

  4. Check again after making changes

    After changing settings, reconnect as instructed by your client and run the DNS test again. “Check again” on this page only refreshes your public IP details; it does not clear the DNS cache or generate a resolver report.

Query privacy and limitations

We don’t log queries. Checks use our GeoIP endpoint to retrieve public IP details. If it’s unavailable, we’ll say so rather than switch to a third-party public API.

The Copy button writes your current IP to the clipboard only when you click it. Before sharing a screenshot, consider masking the full address and any account details. These results do not prove anonymity or guarantee that a particular website will be accessible.

For details on how data is handled, read our Privacy Policy. For help checking your connection setup, see the Getting Started Guide or FAQ.