VPNUQ / Network Records

Public IP & Network Check

Check the address and location visible to websites from your current connection. Results come from VPNUQ’s GeoIP endpoint and describe your outgoing connection; they are not a complete assessment of connection quality or privacy.

How to read the results

Start with your public IP and location, then check the ISP. Proxy detection is for reference only; DNS resolution must be checked separately.

Current Connection

Outgoing Connection Details

The lookup runs automatically when the page opens. After switching routes, run it again to check your new public IP.

GEOIP / RESULT

Checking your current connection…

Public IP
Checking…
Location
Checking…
ISP / Network Provider
Checking…
Proxy Detected
Checking…
Understanding the Results

What These Details Mean

Public IP and Location

Your public IP is the address websites see for your current request. After connecting to a VPNUQ route, compare the lookup result with your selected location. If it still shows your previous IP, check that your client is connected, then run the lookup again. GeoIP locations are estimates based on address data and may not match the actual city.

ISP and Proxy Detection

The ISP is the network provider associated with the IP address in available records; it may not be the brand you pay for your subscription. Proxy detection relies on classifications supplied by the lookup service. “Not detected” does not mean you are not using a proxy, while “detected” alone does not indicate a connection problem. If the service provides no classification, the result will say it cannot be determined for now.

DNS / SELF-CHECK

How to Check for DNS Leaks

This page’s GeoIP lookup can only see the outgoing address for your request; it cannot tell who handled your DNS queries. To check DNS, first review your client’s DNS settings, then check which resolver your device is currently using and compare it with your intended configuration. If they do not match, check your system network settings, your browser’s Secure DNS settings, and whether the client is routing DNS, then reconnect and test again.

A DNS server located in a different region from your outgoing connection does not necessarily indicate a leak. Base your assessment on the DNS path you configured.

First Month Free