Network inspection

My IP and Public Connection Details

Reads your current public connection details through this site's same-origin API. Use it to verify whether your route has switched, whether the location matches your expectations, and how your network provider is identified.

Public IP Country or region ISP Proxy detection

Current connection

Current public connection details

The lookup starts automatically when the page loads. If the API is unavailable, each field clearly shows “Temporarily unavailable”; no third-party public API is used as a fallback.

PUBLIC IP

Looking up

Reading the current connection

IP address: Looking up
Country or region: Looking up
ISP: Looking up
Proxy detected: Looking up

Field reference

What this information means

The results show the public exit point used when your current browser request reached this site. They are useful for a basic post-connection check, but do not represent the network path of every application on the device.

Public IP

This is the public address external websites can typically see. Run the lookup again after switching routes. If the address and location change with the route, your browser traffic is using a new public exit point.

Country or region

The location comes from an IP address database and represents where that address range is generally registered or identified. It is not the device's precise location, and database update timing can cause location differences.

ISP

The ISP field identifies the network operator or autonomous system associated with the public address. Cloud networks, data-center routes, and home broadband may show different organization types; use this as an indication of the exit point's nature.

Proxy detection

This field reports the result identified by the API from characteristics of the current public exit point. A detected proxy does not mean the connection is faulty, while no detection does not guarantee privacy. Check DNS paths and individual applications as well.

Browser extensions, per-app rules, and system routing can send different programs through different exit points. To verify a specific application, repeat the check directly in that application's network environment.

DNS inspection

DNS leak check

Your public IP and DNS resolution path are separate pieces of information. A changed exit address does not automatically mean that domain lookups use the same route.

Record resolution details before connecting

Before enabling a route, check the DNS settings in your system or client. Record the resolver name and its location as a baseline for comparison.

Check client diagnostics after connecting

After enabling a route, check the connection details in your client, your system network settings, or your browser's Secure DNS settings. Confirm how lookups are handled and whether they still point to your original local network provider.

Compare the exit point and DNS locations

If the public exit point is in the selected location while DNS requests continue to be handled by your original network, the DNS path may not have switched with the route. Check split-routing rules, the system DNS cache, and the client's DNS configuration.

Detection limits on this page

A browser does not directly expose complete system DNS resolver information to ordinary web pages. This page therefore shows only public exit data returned by the same-origin GeoIP API and does not present estimates as DNS detection results.

Privacy note

Lookup privacy notice

This site does not record lookup results from this page. The page requests current public exit information only from this site's same-origin GeoIP API and does not connect to third-party public lookup services. If the API fails, the results area retains a clear unavailable state and does not generate substitute data.