IP Check

See the public IP address, location and ISP currently visible to the internet. Results come from this site’s same-site endpoint and can help confirm whether your route has changed.

GEOIP / CURRENT EXIT

Current results

Checking

Public IP: Checking
Country or region: Checking
Internet service provider (ISP): Checking
Proxy detected: Checking

The copy button copies only the current public IP.

$ man geoip

What this means

GeoIP results help show where your current traffic exits the network, but they are not a device-location report or a connection-quality test.

Public IP

Websites usually see your public IP, not the address your device uses on a local network. Check again after connecting to a route. If the public IP differs from before, web traffic is now reaching the internet through a new exit point.

Location

The country or region is inferred from an IP address database and reflects the registered location of the network exit. Database updates can lag; after a data-center move or IP-range reassignment, an older location may appear temporarily.

Internet service provider

The ISP field shows the network operator or data-center name registered to the IP range. It can help identify the exit source, but the name may belong to a parent group, subsidiary or upstream network.

Proxy detection

Proxy detection comes from an IP database label for the address type. “Not detected” does not mean every website will reach the same conclusion; platforms use different databases, update schedules and risk-control rules.

$ resolver.check

DNS leak check

DNS translates domain names into network addresses. If the route has changed but DNS requests are still handled by the original network, the destination and resolution paths may not match.

Record the pre-connection state

Disconnect from the accelerated route, check which DNS servers are active in your system network settings, and record the current exit location. This is your baseline for comparison, so do not rely on a single result.

Check again after connecting

Connect to the target route and refresh this page to confirm that the public IP and location have changed. Then check the connection details in your system or client to see whether DNS is being handled by the current route.

Resolve route mismatches

If the public IP has changed but DNS still clearly points to the original network, reconnect to the route and clear the system DNS cache. If nothing changes, check the client’s DNS-handling option and any manual DNS settings in your system.

$ privacy.query

Lookup and privacy

This page requests only publicly visible network information for the current connection from 23VPN’s same-site GeoIP endpoint. 23VPN does not log lookup contents, send results to third-party public lookup services, or keep them stored in the browser long term.

View privacy policy