Public IP & Network Test

What these details mean

Public IP: the address used for this request

The lookup endpoint sees the address your browser uses to access this site. Test before and after connecting to VPNWei to check whether traffic to this site has changed routes. If your client uses split tunneling, this request may connect directly according to its rules, so an unchanged address doesn’t necessarily mean the entire connection has failed.

Country, region, and ISP: clues about the egress network

Location is estimated using IP databases, which may be out of date and does not indicate your device’s actual location. The ISP field may show a data center, network provider, or organization associated with the address rather than your local broadband provider. Use these details to check your egress, not as a substitute for the target platform’s own region checks.

Proxy detection: a limited assessment

“Proxy detected” means the endpoint identified the current egress as an address associated with a proxy. “No proxy detected” means only that this result didn’t match the relevant detection rules; it doesn’t prove the connection isn’t using a proxy. If the endpoint can’t make a clear assessment, this page shows “Temporarily unavailable” rather than treating missing data as a negative result.

DNS Leak Check

DNS translates domain names into network addresses. A public IP that looks as expected doesn’t mean DNS requests follow the same route. This page checks only your egress details; it doesn’t run a dedicated DNS test, so it can’t determine whether a leak has occurred.

1. Check what your client routes

   First, confirm that your client is connected to the selected route. Then check whether it’s using system proxy settings, split tunneling, or routing all device traffic. DNS handling can vary by mode, so refer to the options and documentation provided by your client.

2. Review your system and browser settings

   Check whether your system’s network settings include a manually specified DNS server, and whether your browser uses secure DNS. A browser’s independent resolver may differ from the system setting; managed work or campus networks may also affect the DNS route. Note your original settings before making changes so you can restore them.

3. Check actual DNS resolution records

   If your client provides DNS logs or diagnostics, revisit the target site and check which server and rules handled the lookup. Cached results may prevent a new request from appearing; consult your operating system’s cache management guidance when verifying. Seeing a resolver associated with a particular region alone isn’t enough to confirm a leak.

4. Keep relevant details if something goes wrong

   Note the selected region, client mode, browser settings, and what happened. If you need help, submit the relevant details through a support ticket. Don’t send passwords or full subscription links. For other connection issues, see the Support page.