VPN connected but real IP is showing: how to fix it

If a VPN says it is connected but your real IP appears to be showing, do not assume every displayed address is the same problem. First establish the browser’s baseline public IP, connect the VPN, and compare the result using the VPN test. This site does not test DNS, and a private WebRTC address or visible IPv6 address is not automatically a real-IP leak.

Diagnose in this order

1. Record the normal public IP in the same browser profile.
2. Connect the VPN and rerun the check after it finishes reconnecting.
3. Decide whether the unchanged result is IPv4, IPv6, a WebRTC candidate, or a DNS concern.
4. Turn off split tunnelling for that browser temporarily.
5. Check whether you used a browser extension instead of a device-wide VPN application.
6. Change server once, reconnect, and restart the browser if necessary.
7. Review the provider’s leak-protection and kill-switch settings.

Common look-alikes

Browser extension versus VPN application

A browser extension may protect only the browser traffic it is configured for. A device-wide app can cover more traffic, but split tunnelling or app settings can still create intended exceptions. Repeat the test in another browser to see whether the symptom follows the browser or the device.

When to consider another provider

Switch only after a repeatable result survives the diagnostic order and the provider documentation cannot explain the platform behaviour. For a full-app comparison, see best VPN with a kill switch, WebRTC protection, and IPv6 protection. If NordVPN’s current documented controls fit your platform, its offer is reasonable to evaluate after this troubleshooting—not before it.

Bottom line

Classify the value first, then change one setting at a time. A stable public-IP comparison is much more useful than a scary “leak” label.