A CLEARER VIEW OF YOUR NETWORK

IPv6 connectivity test

Make separate IPv4-only and IPv6-only requests from this browser. Compare the public exits returned by ipify; opening the page does not start requests.

Network exit

Your next insight starts with a single lookup.

Enable JavaScript to run this tool on demand.

Related network tools

Go deeper. Everything you need to understand your connection.
4 TOOLS

Check both address families

  1. Run the diagnostic on the connection you want to test.
  2. Record the IPv4 and IPv6 results separately. A returned address confirms a response from that endpoint at that time.
  3. If one result is unknown, repeat once and compare another network when appropriate.

The IPv6 request goes to api6.ipify.org, an IPv6-only endpoint. The IPv4 request uses api.ipify.org. A dual-stack endpoint could return IPv4, so it is not used as proof of IPv6 connectivity here.

What a success or failure can establish

A successful IPv6 response shows that this browser reached the IPv6 endpoint. It is not a comprehensive IPv6 readiness score or a test of every website, DNS resolver and protocol.

An unknown IPv6 result can reflect missing IPv6 service, a route or firewall problem, VPN policy, browser restrictions or an unavailable endpoint. IPv4 success with IPv6 unknown does not mean the whole internet connection is offline.

Investigate a family-specific symptom

Use DNS lookup to inspect A and AAAA records for the affected hostname. Compare the browser and VPN conditions before changing router or operating-system settings.

Follow IPv4 works but IPv6 does not and the exit and latency guide. For VPN-specific symptoms, compare WebRTC candidates as additional evidence.

A little more visibility. A lot more confidence.

Transparent sources, useful diagnostics, and reports you can take with you.