Same-Origin GeoIP Lookup

My IP and Public Location

See the IP address, location, and ISP exposed by your current network request. Run the check before and after connecting to compare whether your public exit has changed.

  • Results come from a same-origin API
  • Failed lookups do not use third-party services
  • VPNFF does not log lookup results
Current Lookup Result

Information Exposed by Your Browser

Fetching current public exit information through the VPNFF API.

Public IP
Checking
Country / Region
Checking
ISP
Checking
Proxy Detected
Checking

Copy the current public IP to compare before and after connecting or to troubleshoot connection issues.

Understanding the Fields

What This Information Means

GeoIP results describe the public exit used by the current request. They do not equal the device’s actual location or represent the full network path.

01

Public IP

Websites and online services typically see this address. After connecting to a VPNFF route, run the lookup again. If the public IP differs and its location matches the selected route, browser traffic is being sent through that exit.

II

Country or Region

The location comes from an IP address database and indicates the area where the address is usually registered or used. Databases may lag behind current conditions, so city-level results can differ from the actual data-center location. Use the country or region as the primary reference when checking a route.

03

ISP

This field identifies the network operator associated with the public exit address. After connecting to a route, it will typically change from the local access network to the exit data center or route operator. Compare it with the IP and location fields to assess the connection.

04

Proxy Detection Status

The status depends on network characteristics returned by the API and is intended only as a troubleshooting reference. Databases identify data-center addresses and proxy networks differently, so a single status cannot fully determine connection quality or privacy protection.

DNS Self-Check

How to Check for a DNS Leak

This page’s GeoIP API can show only the public exit for a web request; it cannot directly read the servers handling DNS resolution. A DNS self-check requires comparing the exit location with the resolver information.

  1. Record the Results Before Connecting

    Before connecting to a route, save the current public IP, country or region, and ISP as a baseline for comparison.

  2. Run the Lookup Again After Connecting to the Route

    Confirm that the public IP shown on this page has changed, and check that the country or region matches the selected route. If nothing changes, first check the client connection status and system proxy settings.

  3. Check DNS Information in Your System and Browser

    View the resolver addresses in your system’s network details or on a trusted DNS testing page. If the public exit has changed but DNS requests still point to the original access network, check the client’s DNS handling, per-app rules, and browser Secure DNS settings.

  4. Verify Common Apps Separately

    Browsers, desktop software, and per-app modes may use different paths. Test commonly used apps individually instead of judging all traffic from a single page.

Key point: The public IP and DNS resolution path should match the current route settings. If their locations clearly differ, disconnect and reconnect, then check the DNS and routing options in the client.

Lookup Privacy

VPNFF does not log lookup results from this page. Your browser requests current network information only from a same-origin API, and the page does not forward the result to third-party lookup services. As with a standard web request, the same-origin API must receive the current network address to return the relevant information.

If the API is temporarily unavailable, the results area will show “Temporarily unavailable.” No substitute data will be generated, and fields will not be filled with estimates.

Start Free