IPv6 Test: Check Both Address Families

Keep the browser, network and VPN state stable for the comparison. The two endpoint requests are intended to describe the same connection context. If you change routes during the test, record that change and avoid interpreting the pair as a clean comparison.

Select Check connection to start the independent IPv4 and IPv6 requests. Each endpoint has its own timeout and validated address result. The IPv6 test does not call a dual-stack service and infer both families from whichever route happened to win one request.

Read each outcome separately. IPv4 success and IPv6 failure mean that the first endpoint was reached while the second was not reached successfully in this observation. That is narrower than identifying a broken router, unsupported operating system or unavailable ISP protocol.

If you compare before and after a network change, preserve both observations and timestamps. A temporary provider outage or browser extension rule can affect one endpoint. Repeating the same controlled check can be useful; repeatedly changing several settings at once makes the evidence less clear.

A dual-stack connection can use IPv4 and IPv6, but a single normal website request often exposes only the path actually used. This IPv6 test explicitly queries family-specific endpoints so one result cannot stand in for the other. The component displays the addresses and HTTP timings returned by those observations. Those timings are not equivalent to an ICMP comparison or a broad benchmark of the two protocols. The endpoints, browser behavior and route all influence the measured request duration.

This IPv6 test is deliberately scoped to endpoint reachability. It does not examine every DNS configuration, maximum transmission unit, fallback behavior or application protocol on your network.

Do not compare two HTTP timings as a universal statement that one address family is faster. A useful performance comparison needs matched targets, repeated samples and a defined measurement method.

The two providers’ endpoint requests disclose your source addresses to the service. There is no automatic refresh loop or hidden history. Copy results only when the connection information is necessary for your troubleshooting task.

Consider a laptop whose IPv4 check succeeds and whose IPv6-only request times out. The test establishes two endpoint outcomes, not the location of a fault. You can compare a second authorized connection, such as a different network you normally use, while leaving the browser unchanged. If the outcome changes, that narrows the comparison but still does not identify a particular router setting automatically. Keep both result pairs and their timestamps. A useful IPv6 test report states the services reached, the services not reached and the controlled change between observations.

Keep the question, input, observation time and source together. A bare address, percentage or status code is difficult to interpret later because it omits the connection and measurement context. When comparing two observations, note what changed between them: the target, network, VPN state, selected adapter, record type or remote origin. Change one relevant condition at a time when possible. That makes the comparison easier to explain without inventing a cause from one number.

Save only information you actually need. Network records can reveal infrastructure names and connection details, even when they do not contain a password. Remove unrelated identifiers before sharing a screenshot with another person. Never put private credentials in a domain field or publish an internal hostname as part of a public test. A copied result is a snapshot, not a promise that the same conditions still apply when someone reads it later.

Kepo is a Mac desktop-widget product for repeated checks and small workflows. A labeled troubleshooting note or a supported monitoring widget can keep the relevant context accessible while you work. The download link opens the product workflow; this article does not automatically install a configured diagnostic widget, transfer your network inputs or start a scheduled check. Confirm the actual widget’s capabilities before relying on it for ongoing observations.