VPNDJ / NETWORK CHECK

IP Lookup and Egress Detection

Check where your browser’s request exits to the internet, then see how traffic is routed through your connection and apps.

Current Egress Details

Lookup via our API

Preparing to look up your current egress details.

Public IP: Waiting for lookup
Country or region: Waiting for lookup
Internet service provider (ISP): Waiting for lookup
Proxy detected: Waiting for lookup

Results apply only to this browser request. This lookup does not test DNS or confirm that other apps use the same egress route.

What the results mean

Use egress detection as a point of reference, not as a complete assessment of network security.

IP address and location

The public IP is the address our lookup API identifies when it receives this request. After connecting with a client, run the lookup again and compare the results. If you use split tunneling, this request may use your local network. An unchanged address does not, by itself, mean the client failed to connect.

Location data comes from IP geolocation databases. It may differ from the selected route’s name because of address assignments, database updates, or network routing. It does not pinpoint your device or guarantee that other websites will identify the same location.

ISP and proxy detection

The ISP field shows the provider or network information returned by the API. It may name an internet provider, data center, or network organization. It does not necessarily identify the network your device is connected to, and cannot determine the route type on its own.

Proxy detection relies on the categories returned by the API. “No proxy detected” means only that this check did not flag the request; it does not prove that the connection did not use a proxy. “Proxy detected” does not necessarily indicate a problem. If no clear result is available, this page says “Temporarily unavailable” rather than making an assumption.

How to check a route change
Note your current IP, switch routes in your client, and run the lookup again once the connection is established. Check the client’s connection status, split-tunneling rules, and how the target app is actually accessing the network; don’t rely on the location name alone. If you run into issues, visit the Help Center.

How to Check for DNS Leaks

A public IP lookup and a DNS check are different tests. This page does not test for DNS leaks.

First, check where DNS requests should go

DNS translates domain names into network addresses. Routing an app’s traffic through a selected route does not mean its DNS requests follow the same path. Whether a result counts as a leak depends on your routing setup and privacy expectations—not just the resolver’s location.

Check your client settings. Review DNS, split-tunneling rules, and connection mode to make sure domains that should use the selected route are resolved as expected. If you’re unsure what a setting does, consult the client’s documentation and avoid changing several options at once.
Check your browser settings. Secure DNS or encrypted DNS in your browser may work independently of your system settings. Note the current configuration and make sure it matches your client setup. Don’t disable security features just to get a particular test result.
Check your system and apps. Custom system DNS, other network tools, and an app’s own DNS features can affect routing. After changing settings, reconnect and reopen the app you’re testing to reduce confusion from existing connections or cached data.
Use a dedicated test before drawing conclusions. For a hands-on check, use a reputable DNS testing tool and compare the reported resolver network with your expected setup. The test will generate additional network requests, so review the tool’s privacy policy first.

A resolver in your local area does not necessarily indicate a leak, and one in another region does not necessarily mean your setup is working as intended. If test results don’t match your settings, contact support through the control panel with your client platform, connection mode, and a description of the issue with sensitive details removed. Do not share your subscription URL or account password.

Read the guides →

Privacy and Lookup Limitations

VPNDJ does not log lookups. This page requests current egress details through our API, does not fall back to a public third-party lookup service, and does not save lookup history in your browser. Clicking “Copy IP” only copies the displayed address to your clipboard.

The lookup sends a network request to our API, so the API receives the egress address for that connection. If the API is unavailable, this page clearly says “Temporarily unavailable” and does not substitute a sample address. Before sharing a screenshot, consider hiding any IP or network details you don’t want to make public.

Read the Privacy Policy →