Public IP and location

Understanding the results

Public IP: where your request reaches the site from

This is the public IP address seen by this site’s lookup API, not your device’s address on the local network. After connecting to VPNPaper, the public IP will typically change if your browser’s request goes through the selected route. This lookup only shows the path used by this request; it cannot tell you whether other apps use the same route.

Location and ISP: address data, not precise location

Country and region data comes from IP databases and may differ from route labels, data center locations, or provider registration details. ISP usually refers to the network provider associated with the address, but may show the data center operator instead. Database updates can lag, so don’t use this information to infer a device’s actual location.

Proxy status: a helpful indicator, not an account access pass

Proxy status is shown only when the API explicitly returns a result. No proxy detected does not mean every website will reach the same conclusion; third-party services may also assess your account region, sign-in activity, and their own rules. If the API returns no status, this page will show “Temporarily unavailable” rather than treating missing data as no proxy detected.

DNS leak check

DNS translates domain names into network addresses. A changed public IP doesn’t mean DNS requests take the same route. This page only checks your public IP; it doesn’t run a DNS leak test, and IP location data can’t tell you whether DNS is leaking.

1. Record your public IP before and after connecting. Check the result before connecting, then select “Look up again” after connecting. If the IP hasn’t changed, check your connection and routing settings before investigating DNS.
2. Check your DNS settings. Review the client’s DNS interception options and the encrypted DNS settings in your operating system and browser. A browser’s separate DNS service may differ from the one used by the client, so check your actual configuration.
3. Verify the actual DNS route. Run a test with a trusted DNS testing tool or check the client logs to see where DNS requests are sent. The tool shows the resolver’s exit location; matching or different place names alone don’t prove anything.
4. Adjust settings and test again. Follow the client’s instructions to adjust DNS interception and routing rules, reconnect, and run another test. Avoid changing many options at once during troubleshooting, so you can identify which setting affects the result.

This page does not automatically send requests to external DNS testing services. Before using another testing tool, check how it handles your data.