This browser’s network egress

IP Address Checker

See where this request connects to the internet. Check again after connecting to a route to compare your public IP and location.

Connection details

Not checked yet
Public IP address
Temporarily unavailable
Country or region
Temporarily unavailable
Internet service provider (ISP)
Temporarily unavailable
Proxy detected
Temporarily unavailable

Enable JavaScript to check your current public IP.

What these results mean

Public IP address: the source of this request

This is the public IP address seen by our API, not your device’s local network address. After connecting to VPNFresh, requests from your browser will usually show the exit IP of the route you selected. Per-app proxy settings, split tunneling, or browser proxy settings may give different apps different exit IPs.

Location and ISP: information from IP databases

Location data comes from IP databases and may lag behind network changes; it does not show your device’s precise location. An ISP is the network provider or operator associated with an IP address. On international routes, it’s common to see the name of a data center or network operator. Don’t rely on these details alone to decide whether a route is working.

Proxy detection: a signal, not a verdict on your connection

Detection results depend on the data and methods used by the API. “Not detected” doesn’t prove that your request isn’t going through a proxy, and “detected” doesn’t mean your connection has a problem. If the API doesn’t provide a clear status, this page shows “Temporarily unavailable” rather than treating missing information as a negative result.

How to check for DNS leaks

DNS translates domain names into IP addresses. Routing web traffic through a proxy doesn’t mean DNS queries follow the same path. This page checks the exit IP for HTTP requests; it doesn’t collect a list of DNS resolvers or report whether DNS is leaking.

  1. Check your client’s DNS settings

    Review the DNS and routing settings in your client, and make sure domain lookups are handled as expected by your connection. Options vary by client; if you’re unsure, leave the settings unchanged and consult the advanced section of the complete guide. Avoid entering unfamiliar DNS addresses.

  2. Check your browser and system settings

    Secure DNS in your browser, custom system DNS settings, and other networking tools can change the route DNS queries take. Check each setting against your expectations, and avoid changing several options at once, which can make problems harder to diagnose. Using encrypted DNS does not, by itself, mean a leak has occurred.

  3. Test web traffic and DNS separately

    Use this page to check the exit IP for web requests. To determine the DNS route, use a diagnostic tool that can observe DNS queries and review its privacy policy. A difference between the resolver’s location and your exit location does not, on its own, prove a leak; consider your client’s rules and diagnostic results together.

If a result doesn’t match your expectations, contact support through the user dashboard and describe your device platform, client settings, and what you observed. Before sharing screenshots, hide subscription links, credentials, and other personal information.

Query privacy

We don’t log queries. Requests go only to our own API; we don’t fall back to third-party public lookup services. This page doesn’t save results in your browser’s local storage. Copying happens only when you click the button, and copies only your public IP. Learn more in our Privacy Policy.