VPNMF / Network Test
Public IP & DNS Check
See the network route your browser is currently using. After switching routes, run the check again to compare your public IP and its reported location.
Current route
Waiting for check- Public IP
- Temporarily unavailable
- Country / region
- Temporarily unavailable
- Internet service provider / ISP
- Temporarily unavailable
- Proxy detected
- Temporarily unavailable
What these results mean
Public IP: the address websites see
Your public IP is the network address identified when this request reaches the test endpoint. Enabling a proxy doesn’t guarantee that your browser uses it: routing rules, browser extensions, and system proxy settings can all affect the request path. This page uses a VPNMF endpoint. If your rules send VPNMF directly, seeing your local network’s public IP may be expected with your current setup.
Country, region, and ISP: registration data, not precise location
The country and region come from IP registration data. They may differ from the location shown in your client because of address reassignment or outdated databases. ISP refers to the provider or network associated with the address returned by the endpoint; it may be a data center operator rather than your internet provider. These results can’t pinpoint a person’s home address or prove where a route is physically located.
Proxy detection: an indicator, not proof of connectivity
This page shows “Proxy detected” or “No proxy detected” only when the endpoint explicitly returns a proxy status. If that field isn’t available, the result is “Temporarily unavailable.” No proxy detected doesn’t mean your connection isn’t using one, and proxy detected doesn’t guarantee that a particular website will work. AI Tools and Streaming services apply their own location and risk checks, so verify access on the service itself.
To troubleshoot routing rules and connection settings, see our Getting Started Guide. For regional checks on AI Tools, read the AI Access Guide.
DNS / resolution path
Check for DNS leaks
DNS translates domain names into network addresses. Even when web traffic passes through a proxy, DNS requests may take a different route. This page checks your public IP, not your DNS resolver, so it can’t determine whether a DNS leak is present.
-
Check your client’s DNS settings
Open the network or DNS settings in your client and confirm that it handles DNS requests as expected. Options vary by platform, so check the documentation for your client. A setting labeled “encrypted” doesn’t by itself confirm that DNS requests are taking the expected route.
-
Check your browser and system DNS settings
Secure DNS, custom resolvers, and system network settings may override your client’s expected behavior. Note your current settings first, then check for conflicts with the client. Encrypted DNS protects DNS requests in transit; it doesn’t guarantee that requests leave through your selected route.
-
Verify with logs and real requests
If your client supports it, check connection logs or DNS diagnostics. Visit a domain that hasn’t been cached and verify which outbound route the DNS request uses. Hide addresses and account details before sharing logs. Seeing a resolver address in system settings alone doesn’t reveal the route an actual request takes.
-
Don’t assume what you can’t verify
If your client doesn’t show the DNS request path, don’t treat the public IP on this page as a DNS test result. To get troubleshooting advice, describe your platform, client settings, and what you’re seeing in a support ticket in the user panel. Don’t include your password or full subscription link.
Lookups and privacy
VPNMF doesn’t log lookups. Check requests are sent only to a VPNMF endpoint to return your current network details; third-party public lookup services aren’t used as a fallback.
Results stay on this page. Nothing is copied until you select the copy button. Your public IP is network information, so check who will see it before sharing a screenshot or copied result.
View Privacy Policy →