Why hasn’t my IP changed?
Compare fresh browser requests before and after a network change, then check the scope of your VPN or proxy.
In short: Record your IP, change one thing (connect the VPN, switch server, or switch network), then refresh and compare. A same-IP result means the browser's requests still leave through the old address; check split tunneling and per-app rules before blaming the VPN.
Last updated
Start with an observation
Compare two browser lookups
Use the before-and-after controls on My IP. A lookup is a snapshot of one request, not a VPN status detector.
Open My IP →1. Record, switch, then refresh
- Wait for a successful IP lookup and select Record current IP.
- Keep the tab open. Change one thing: connect your VPN, change its server, or switch networks.
- Select Refresh and compare. Check that the after observation time belongs to the new lookup.
If the new lookup fails, refresh again. The page keeps your before snapshot, but it cannot compare a missing after address.
2. Read what changed
- Same IP: NetOkay saw the same public address for both requests. This alone cannot tell whether the VPN is connected or whether another application uses it.
- Different IP: the browser’s observed public address changed. This does not verify every application or destination.
- Different address families: one request used IPv4 and the other IPv6. Compare like-for-like requests before drawing a routing conclusion.
3. Check the settings you already have
Confirm the VPN has finished connecting. Review split tunneling and per-application rules: the browser may be excluded, or only selected destinations may use the VPN. A browser extension may also have a different scope from a system VPN.
Review the client’s own connection status and routing documentation. Change one setting at a time and repeat the comparison. These observations do not establish a DNS or WebRTC leak, and do not require buying another VPN.
4. Compare the application separately
If your browser works but another application does not, use Compare environments and inspect that application’s own settings. Matching browser and terminal IPs still do not prove identical full paths.
Before and after data stays in this tab’s memory. Leaving, reloading, or returning to the page clears it.