Current connection

NETWORK INSPECTION

Public IP and network check

View the IP, location, ISP, and proxy status visible to websites for your current connection. Results come from an on-site, same-domain lookup and do not use third-party public lookup services.

CURRENT CONNECTION

Check results

Loading network information…
Current public IP
Loading…
Country or region
Loading…
ISP
Loading…
Proxy detected
Checking…

RESULT GUIDE

What these details mean

Public IP

Your public IP is the network address websites and online services see. After connecting to an international route, it should normally show the address used by that route. If it still matches your original network, confirm that the client is connected and that your routing rules cover the service you are accessing.

Country or region

The location is based on network databases associated with the IP address and indicates its approximate location. Database update schedules and regional boundaries vary, so use this result to verify a connection rather than as precise location data.

ISP

The ISP field shows the network operator or autonomous network organization associated with the public address. It can help indicate whether the request comes directly from your local network or has reached another network exit through the selected route.

Proxy status

This status only reports the conclusion returned by the lookup interface. A detected proxy does not necessarily indicate a connection problem; network acceleration, enterprise gateways, and relay routes can all produce similar characteristics. If the interface returns no clear conclusion, the page shows “Unable to determine at this time” rather than inferring one from the location.

DNS REVIEW

DNS leak check

A normal public IP does not necessarily mean that DNS requests follow the same network path. This page’s GeoIP lookup does not enumerate DNS resolvers, so a single IP result is not presented as a complete DNS test.

Check the exit location first

Note the country or region and ISP shown on the results card, and confirm that they match the selected route. If the exit itself is unexpected, resolve the connection or routing issue before continuing with the DNS check.

Check system and browser settings

Review your system network settings and the browser’s Secure DNS settings to see whether a separate resolver has been configured. A resolver enabled only in the browser may use a different path from the system network.

Compare resolver ownership

Use a trusted DNS testing environment to check the resolver’s region and network organization. If it still points to the original network and clearly differs from the current exit, review the client’s DNS takeover and routing configuration.

Verify after reconnecting

After changing settings, disconnect and reconnect the current route, then check the exit and resolver details again. Browser caches may retain earlier results, so close the relevant pages and reopen them before verifying.

A difference between DNS ownership and the exit location does not necessarily indicate a leak. Enterprise networks, encrypted DNS, and cross-region resolvers can all produce differences; assess the result alongside your network settings and route configuration.

Privacy note

VPNHT does not log queries made on this page. Requests are sent only to VPNHT’s same-domain GeoIP interface; the page does not submit results to third-party public lookup services or persist check data in the browser. The copy function handles only text already displayed on the page.