NETWORK / DIAGNOSTIC

IP Address & Network Test

View public information about your current network exit. Results come from UQVPN’s same-origin GeoIP endpoint and help verify your route exit, region, and ISP.

Public IP Country / Region ISP Proxy Check

LIVE RESULT / SAME ORIGIN

Current exit information

The UQVPN test endpoint is requested automatically when the page loads. Unavailable data is never replaced with estimates.

Retrieving network information
GEO / LOOKUP
IP address
Checking
Country / Region
Checking
ISP
Checking
Proxy detected
Checking

This lookup displays only public network information returned by the endpoint.

FIELD NOTES

What this information means

Each result answers one specific question. To verify that a route matches expectations, review the exit address, region, ISP, and proxy status together.

IP

Public IP

This is the public exit address that target websites can typically see. If it changes after connecting to a route, the exit path for network requests has changed. The address alone does not indicate speed or confirm that DNS is configured correctly.

GEO

Country / Region

The location is mapped from the public address range in a GeoIP database. It is useful for checking the exit’s approximate region, but database updates may lag, and city-level results may differ from the data center’s actual location.

ISP

Network provider

The ISP field identifies the network organization or provider associated with the current exit address. It can help distinguish local broadband, data centers, and other network types, but the displayed name depends on address registration data.

PROXY

Proxy check

This result reflects only the identification status returned by the GeoIP endpoint. Different websites may use different address databases and detection rules, so treat this result as route verification information rather than a universal conclusion for every target service.

DNS / CHECKLIST

DNS leak check

A correct public IP does not mean DNS requests necessarily follow the same path. DNS queries may be handled separately by the system, local network, browser, or client, so they require an independent check.

  1. Verify the exit region first

    After connecting to the target route, refresh this page and confirm that the country or region matches the selected exit. If the exit itself is incorrect, resolve the route connection issue before checking DNS.

  2. Check the resolver used by your system

    Use your system network settings or a terminal command to check the current DNS servers. Record the resolver addresses and their source, then confirm whether they are provided by the acceleration client, secure system DNS, or local network.

  3. Check the browser’s separate settings

    Some browsers can enable secure DNS independently, using a resolution path that differs from the system settings. Check both the browser and operating system configuration to avoid reviewing only one.

  4. Compare different connection states

    Switch routes and check the exit and resolver source again. If DNS continues to be handled by an unexpected network, adjust DNS takeover settings in the client and verify once more.

Start Free