How to Check Your Public IP Before and After Connecting to a VPN
Your VPN app says it’s connected. Which IP address does a website see? A before-and-after comparison on the same network can tell you which address a particular web request used. Pick a trusted HTTPS lookup service. There’s no need to sign in or install an extension for this check.
How to verify your VPN exit IP before and after connecting
Use the same browser and trusted lookup page to record the public IP before connecting, then refresh after connecting. Compare IPv4 and IPv6 separately if the test reports both. If the address stays the same, check whether the current VPN configuration routes that browser through the tunnel, and confirm which server the app selected.
Related guide: First VPN Connection Checklist After Your Plan Activates
Find the address worth comparing
An IP lookup service reports the address it sees on an incoming request. Your device’s network settings usually show an address used on the local network. A laptop might have 192.168.1.25 at home, while an ISP might use addresses from the shared 100.64.0.0/10 block upstream. The router’s WAN address can differ from the address a website sees.
Record IPv4 and IPv6 in separate columns. IPv4 looks like four groups of digits separated by periods. IPv6 generally contains colons. One lookup can use just one address family. If the service doesn’t report an IPv6 result, write “not tested” in that column so you don’t mistake a missing reading for a confirmed result.
Run three checks on one network
- Before connecting
Record the baseline - While connected
Record the new exit - After disconnecting
Check for a return to baseline
Disconnect the VPN and note the time and address returned by the lookup page. Keep the device, Wi-Fi connection, and browser the same. Connect the VPN, wait for the client to report a connection, then reload the same page. If the service offers separate IPv4 and IPv6 checks, run both. Disconnect and check one more time to see whether the address returns to the original baseline.
Keep any browser proxy settings the same throughout. If an extension can change your browser’s route, repeat the experiment in a clean browser profile and record which profile you used. Switching from Wi-Fi to cellular midway through the test adds another variable and can change the public address by itself.
Decide what each result calls for
| What you observe | What to check next |
|---|---|
| IPv4 changes and returns to the baseline | The lookup used a different IPv4 exit. Test another app separately if its route matters to you |
| IPv4 changes while IPv6 stays the same | Confirm both IPv6 readings came from live requests, then check your provider’s IPv6 coverage |
| The readings are identical | Check for stale results, proxy settings, split tunneling, and the address family used before trying another lookup service |
| The IP changes but the city does not | Compare the addresses themselves. Several exits can share the same estimated city |
The results describe requests sent to the lookup service. A split-tunneling rule may send another browser or video app along a different route. If a result looks inconsistent, repeat the same experiment on a second trusted network.
Share the evidence that helps support
Include your device, operating system, client version, test time and time zone, and what changed. “Windows on the same Wi-Fi, IPv4 changed after connecting, IPv6 wasn’t tested” is easier to investigate than a screenshot showing only a location.
Before posting a screenshot publicly, cover full IP addresses, account details, and unrelated tabs. If one particular app matters, name it and describe any split-tunneling settings so support can suggest a targeted test.