Tool guide limitationsGuides explain the intended workflow but cannot cover every device, provider or operating condition.
Interfaces and external services can change. Follow the current on-screen controls, check dates and vendor documentation, and verify important results independently before acting on them.
Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.
Connection tests
IPv4 and IPv6 Readiness guide
Observe whether the browser can use IPv4 and whether an IPv6 route is selected.
Open IPv4 and IPv6 ReadinessWhat you need
- No address is required
How to use it
- 1Start the readiness check.
- 2Wait for IPv4 and dual-stack requests.
- 3Review the observed protocols.
- 4Export the result if needed.
Understanding the results
- Observed IPv6 demonstrates one selected route; not observed does not prove IPv6 is unavailable everywhere.
Recommended next actions
- Compare with operating-system and router status on an authorised network.
Common problems
- VPNs, privacy relays and browser routing can mask the underlying network.
Privacy and security
- Public address services see the requesting connection; the page avoids storing the address in health history.
Worked example
- Scenario
- Checking a dual-stack connection
- Example input
- Run with VPN disabled where appropriate
- How to read it
- IPv4 success plus an observed IPv6 address indicates the browser selected both protocols during the check.
Limitations
- This is a browser-route observation, not a complete router or ISP audit.
Do not rely on one result for a production, security, safety, purchasing or contractual decision. Verify important findings independently.