Get IP Status

Connection test

IPv6 test: check your connection.

Find out whether this browser can reach our IPv4-only and IPv6-only endpoints. Each successful request shows the address the endpoint saw. The test checks this service, not every destination on the internet.

IPv4
Not tested
IPv6
Not tested

Start the test to check both address families.

A failed test can mean a network, DNS, browser or test-server problem. “Not detected” is not proof that your network has no IPv6.

IPv6 not detected? Follow the troubleshooting steps.

How to read your IPv6 test result

Detected

The corresponding endpoint responded with a valid address of that family. The request worked for this browser at that time.

Not detected

The request failed. Network configuration, DNS, a VPN, filtering or endpoint availability can cause this.

Timed out

The request did not complete within 4.5 seconds. Try again and compare another device or network if the result persists.

Not configured

The service has no test endpoint configured for that family.

Test unavailable

The test could not use the configured endpoint or its response. This can be a service problem; it does not diagnose your connection.

If IPv4 is detected and IPv6 is not, many websites can still work over IPv4. If both are detected, both endpoints responded. Translation or a proxy may be part of the path, so this does not prove native dual-stack service. Neither outcome certifies a VPN, tests every application or proves that inbound connections are allowed.

Why this may differ from your main IP address

The home page shows the address used to load it. A browser on a network with both address families can choose either one for that request. The separate tests above check each family individually. A VPN or proxy may also handle them differently.

Learn how IPv4 and IPv6 differ, or follow IPv6 troubleshooting to narrow down a failed test.