Both confirmed
Your connection reached both dedicated endpoints. This is evidence of working dual-stack connectivity on the tested paths.
Check whether your connection can reach the internet over IPv4, IPv6 or both.
Testing a separate endpoint for each address family.
Run the check to see the measured values.
IPv4/IPv6 checks contact Localtonet and may use ipify when a Localtonet endpoint cannot be reached. A failed check does not prove IPv6 is unavailable on your network.
IPv6 is a newer IP addressing protocol with a much larger address space than IPv4. A dual-stack connection supports both, but a normal website visit only shows the path your browser selected for that request.
This test uses separate IPv4-only and IPv6-only endpoints so each path is checked independently. IPv4/IPv6 checks contact Localtonet and may use ipify when a Localtonet endpoint cannot be reached. The measurements identify the service used for each observation. If IPv6 is not confirmed, review the ISP-facing router and VPN settings, then repeat the test on another network to narrow down the cause.
Your connection reached both dedicated endpoints. This is evidence of working dual-stack connectivity on the tested paths.
Your browser reached the IPv6-only endpoint over IPv6, with no IPv4 fallback on that hostname.
Your ISP, VPN, firewall or DNS settings may be involved. A temporary failed request does not prove IPv6 is permanently unavailable.
Check your router and VPN IPv6 settings, then check again. Test after a network change to compare the result.
Yes. On a dual-stack hostname, the browser chooses a working path. That choice does not describe every available path.
Yes. A VPN may support, block or route IPv6 separately from IPv4.
No. DNS, routing, browser policy or a temporary endpoint issue can also prevent the request.