Short answer: A useful VPN troubleshooting flow starts before the VPN connects, records the visible IP/DNS/WebRTC/IPv6 state, connects the VPN, retests, then uses Safe Copy. This separates normal VPN routing from DNS mismatch, WebRTC exposure, IPv6 behavior, and device-specific setup problems.
Use this hub when a VPN is installed but the result is unclear: IP still shows, DNS country differs, streaming devices use router VPN, iPhone disconnects, or kill switch behavior needs a practical check.
Quick answer
- Start with VPN Leak Test and run it twice, once before connecting and once after, because on this topic the useful signal is the difference rather than either reading alone.
- Compare network owner and ASN rather than the city. Geolocation databases lag behind provider routing and disagree routinely.
- IP, DNS, WebRTC and IPv6 can each follow a different route, so a correct visible IP does not settle the other three.
- Change one layer at a time. Several changes at once produce a result that cannot be attributed to any of them.
VPN Setup & Troubleshooting at a glance
| Signal | What it means | Best next step |
|---|---|---|
| Before state | Your normal IP, DNS, WebRTC, IPv6, and browser signals before VPN. | Save the baseline first. |
| Connected state | What changes after the VPN connects. | Run VPN Leak Test again. |
| IP still shows | The visible IP may be the VPN endpoint or the original ISP route. | Compare network owner, ASN, and expected country. |
| DNS mismatch | DNS can differ because of browser Secure DNS, router DNS, ISP DNS, or VPN DNS. | Run DNS Leak Test after the VPN check. |
| WebRTC/IPv6 | Browser candidates and IPv6 can behave differently from the page IP. | Run WebRTC and IPv6 tests as follow-ups. |
| Receipt | A safe receipt makes support or personal troubleshooting easier. | Use Safe Copy after re-test. |
Limits and methodology
MyIPScan topic hubs organize practical checks around observable browser and network signals. Results are snapshots for this browser, device, network, and time. They do not prove full anonymity, do not replace provider documentation, and do not test every app on the device.
For transparent limits, see the MyIPScan methodology, editorial policy, and author profile.