IP LOOKUP

IP Lookup: Public IP & Location Check

Open this page while connected to VPNFP to confirm whether your traffic is going through the optimized route. Data comes from our own GeoIP endpoint — the lookup never passes through a third-party service.

Exit IP Looking up…
Country / Region Looking up…
ISP Looking up…
Proxy Detection Looking up…

If the endpoint hiccups occasionally, wait a moment and click "Check Again"; when no data comes back, the page shows "Temporarily unavailable" rather than a guess.

READING THE RESULT

What these results mean

Exit IP: the address websites actually see

This is the address a website's server records every time you visit. Without an optimized route, it's assigned by your local ISP; once you connect to VPNFP and pick a node, it should switch to the node's exit IP. If this page still shows your local ISP's address, your browser traffic isn't going through the route — confirm the client is connected, then reload this page and compare.

Location & ISP: labeling the exit point

The location comes from public IP geolocation databases and shows the registered country, city, and operator behind the address. After connecting, seeing node cities such as Hong Kong, Tokyo, Singapore, or Frankfurt — along with the corresponding datacenter provider — means the exit has switched. City-level labels can occasionally be off, so judge by the country level.

Proxy detection: a database flag, not a fault

This field shows whether the IP is flagged in databases as a datacenter or proxy exit. Seeing "Proxy / datacenter detected" while using an optimized route is normal — it only means the exit is a datacenter IP, not that something is broken. A "No proxy detected" result means the exit looks like a regular network in the database.

DNS LEAK CHECK

DNS Leak Check

A DNS leak means your main traffic goes through the optimized route, but DNS queries are still handed to your local ISP — the sites you visit could leave traces at the resolution step. No extra tools are needed; this page is enough:

  1. Record a baseline. Open this page without connecting, and note your current exit IP and ISP.
  2. Connect to a node. Open the VPNFP client, pick a node, and wait until the client shows connected.
  3. Reload and compare. Come back to this page and refresh: the exit IP should now be the node's IP, with the location and ISP switched to the node's region.
  4. Spotting problems. If the exit IP has switched but sites outside your region still won't load or resolution is noticeably slow, DNS may still be going through your local ISP. Enable remote DNS in the client (or switch the client's built-in DNS setting) and try again.
Note: The VPNFP client resolves domains inside the tunnel, so no extra setup is needed when the connection is working; the steps above are for pinpointing problems when it isn't.
Privacy note: The lookup on this page runs directly from your browser to our GeoIP endpoint; results are rendered only in this page, and we store no query logs. For how data is handled at the service level, see "Privacy Policy" in the footer.