IP diagnostics

IP Leak Test

Run an IP leak check after connecting to VPN, proxy, Clash, V2Ray, or mobile clients, and compare public IP with DNS and WebRTC signals.

Updated: 2026-05-11

Open NetScope

Direct Answer

An IP leak test confirms what public address websites see. It should be paired with DNS and WebRTC checks because a changed IP alone does not prove the route is clean.

Start with public IP

Check whether the visible IP, country, ASN, and provider match the expected VPN or proxy route.

Compare other signals

DNS, WebRTC, time zone, and browser language may still reveal inconsistencies.

Retest after route changes

Switching nodes, Wi-Fi, or mobile networks can change leak behavior.

Steps

Connect to the route.
Check public IP and country.
Run DNS and WebRTC checks.
Refresh after switching nodes or networks.

Checklist

Visible IP changed from the original network.
ASN and region are expected.
DNS does not point to the original ISP.
Browser signals are consistent.

Troubleshooting

IP does not change

Enable system proxy, VPN mode, or global/TUN mode in the client.

IP changes but DNS does not

Fix DNS settings and retest with global mode.

Different sites show different locations

Geolocation databases differ; focus on whether the original IP is exposed.

DNS leak test Check resolver exposure. WebRTC leak test Check browser-level exposure. VPN speed test Measure route stability. Proxy checker Test nodes before use.

FAQ

Is a changed IP enough?

No. DNS and WebRTC can still expose unexpected signals.

Why do IP locations differ?

IP geolocation databases are inconsistent. The main check is whether the original network is visible.

Should I test every node?

Test any node you plan to use for important browsing or account activity.