Guest Network · Connection Check

VPNGuest Network Check

First, see where your browser’s connection appears to come from, then check whether it matches your expectations. The result applies only to this query’s public IP, not the network routes used by every app on your device.

Current connection details

Queries aren’t logged

Getting your browser’s connection details…

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

After switching routes, wait for your client to connect, then check again. This page does not run an automatic DNS leak test.

What these results mean

Compare your public IP before and after connecting, then consider what you can actually access. No single field can confirm your connection status on its own.

Public IP: the address websites see

This is the public IP our API detected for this request, not your device’s address on your local network. Check before and after connecting to see whether your browser’s public IP changes. If it doesn’t, make sure your client is connected and that your routing rules send requests to this site through the selected route.

Country or region and ISP: useful for cross-checking

Location data comes from an IP database, not device location services. Database updates and IP assignments can differ, and the ISP field may show a data center or upstream network. Use these details as supporting clues, not as definitive proof of a route’s physical location. AI tools and streaming platforms may also use their own location checks.

Proxy detection: not a privacy or availability verdict

“Proxy detected” means the API has flagged this public IP as proxy-related. “No proxy detected” means only that the API did not return that flag for this check; other websites may reach a different conclusion. If the field is missing, it stays “Temporarily unavailable” rather than being treated as a negative result. Check account eligibility, service regions, and platform restrictions separately.

Check for DNS leaks

Checking your public IP and checking DNS are separate steps. This page’s API does not return DNS routing details, so it cannot automatically determine whether your DNS is working as expected or leaking.

Check your client’s DNS settings.
See whether your current mode handles DNS requests and whether your routing rules use different DNS routes for different domains. If DNS should go through the selected route, first confirm that the relevant client settings are in effect rather than relying on the connection toggle alone.
Compare your system and browser settings.
Custom system DNS, browser Secure DNS, and your client’s DNS settings can all be active at once. A DNS service set directly in your browser may use a different route. If settings conflict, note the original configuration, then make changes according to your client’s instructions. Changing several settings at once can make troubleshooting harder.
Check DNS request logs, if available.
If your client provides local diagnostic logs, check how DNS requests are routed when you visit the site in question. Using a third-party DNS resolver does not automatically mean there’s a leak. What matters is whether requests follow your intended route and whether they reach a local resolver you meant to avoid. A change in public IP alone cannot verify DNS routing.

For more help, start with our Guides. If AI tools show a region warning or stop responding, follow the AI troubleshooting guide to check each setting.

Privacy and troubleshooting

Queries aren’t logged. This page retrieves results through VPNGuest’s own API, does not forward checks to public third-party lookup services, and does not save lookup history in your browser. Returning a result requires processing the public IP for this request; this is not the same as device location tracking. See our Privacy Policy for details on data handling.

If the result says “Temporarily unavailable,” first make sure you can reach this site, then select “Check again.” A timeout, interrupted connection, or incomplete response can cause a lookup to fail; this does not mean your route is disconnected. For help, open a ticket through the user dashboard and include your platform, connection mode, and any error message. Before sharing a screenshot, hide any personal network details that aren’t needed.