Your IPv4Waiting
Ready to check in your browser
Your address appears here when the check completes.
Connection diagnostics
Three routes. One connection.
Test IPv4, IPv6, and dual-stack HTTPS connectivity and compare public addresses before and after changing networks or enabling a VPN.
Your IPv6Waiting
Ready to check in your browser
Your address appears here when the check completes.
Dual-stack routeWaiting
Ready to check in your browser
Your address appears here when the check completes.
Before & after
What changed on your connection?
Save the current results, switch Wi-Fi or connect to your VPN, and check again. Compare the addresses exposed by these HTTPS requests. A changed address alone does not prove that all traffic uses a VPN.
Nothing is stored in cookies or local storage. The baseline disappears when you leave or reload this page.
Session history
Follow a connection change
Each manual check captures the three endpoint results. History is held in this page’s memory and disappears on reload. Request durations include DNS, TLS, proxy, application, and network work; they are not ping or a speed score.
Run a check to begin a new session history.
Router WAN comparison
Could another NAT device be upstream?
Enter the IPv4 shown under WAN / Internet in your router’s status page. This browser-only comparison checks common private/shared ranges and compares it with the public IPv4 observed above. It does not contact your router or scan any address.
Use values from the same network and time. A browser VPN or proxy can change the public result. The WAN input stays in this page and is excluded from exported reports.
Read the NAT and CGNAT guide →Check from your own device
Separate the browser from the network
These commands make outbound requests from your device to myip.dk and inspect your local configuration. Run them in your own terminal to compare with the browser result.
curl -4 --connect-timeout 5 --max-time 10 https://myip.dk/api/ip
curl -6 --connect-timeout 5 --max-time 10 https://myip.dk/api/ip
# Linux: IPv6 addresses and default route
ip -6 address show
ip -6 route show defaultThe ip commands shown are Linux-specific. Both curl family checks also work on macOS. A curl result describes that terminal’s route, which can differ from a browser proxy.
Inspect the IPv6 endpoint’s DNS records →How to read the results
An IPv6 success means this browser reached our IPv6-only hostname. Dual-stack shows which address family the browser used when both were available; it is normal for that choice to change.
“Not reached” is inconclusive. A missing IPv6 route is one possibility, but DNS failures, VPN settings, filtering, extensions, and service outages can produce the same result.
Troubleshoot IPv6What this test measures
The connection runs from your browser to our network edge, which forwards the observed address to our server. It does not measure a direct route to the origin server, bandwidth, latency, or inbound connectivity.
A successful HTTPS test cannot establish whether DNS, WebRTC, or every other application follows the same route.
Understand VPN comparisons