Save a baseline, then change one thing
Record both public address results before connecting a VPN. On the connection page, label the next check and choose any saved check as your baseline. Connect the VPN, wait for the client to report that the tunnel is ready, and check again in the same browser. Compare addresses, successful and unsuccessful families, and timestamps. The last 20 checks remain in this page’s memory until you leave or reload.
A changed address shows that the observed path changed. It does not prove that every application, DNS query, or destination now goes through the tunnel. Split tunneling can send selected traffic outside a VPN by design.
Worked example: IPv4 changes but IPv6 does not
Before connecting, both families succeed. After connecting, IPv4 changes to a hosting network while the IPv6 address is unchanged. That is a reason to inspect the VPN’s IPv6 and split-tunnel settings. It is consistent with the browser’s IPv6 request still using the original path, but this page cannot inspect the VPN configuration to confirm the cause.
If IPv6 becomes unreachable after connecting, the VPN may intentionally block it. An unavailable result alone does not tell you whether that is the intended policy, a routing issue, or a temporary failure.
A repeatable comparison
Keep the experiment small so the result is easier to interpret.
- Use the same network and browser for both measurements.
- Avoid switching Wi-Fi, VPN location, and browser proxy settings at the same time.
- Check both address families and keep failed results in the report.
- Consult your VPN client’s route and application exclusions if results do not match your intended setup.
- Repeat after a reconnect if you are investigating an intermittent problem; an address change can also come from normal ISP allocation.
This is not a DNS or WebRTC leak test
Our DNS lookup queries public resolvers from our server, so it cannot identify which resolver your browser or operating system normally uses. These HTTPS address checks do not inspect WebRTC candidates, VPN encryption, kill-switch behavior, or traffic in other applications.
Connection reports and JSON exports contain your addresses, any labels you typed, the session history, and the selected baseline. Review the downloaded report before sharing it. HTTPS request durations include application and network work and are not ping or bandwidth measurements.