The current-request result shows the protocol used to reach LumaProbe. The domain check retrieves public A and AAAA records. These are two separate facts: using IPv4 here does not prove that the device or provider lacks IPv6 elsewhere.
An IPv6 request confirms usable IPv6 on this route. An AAAA record means a domain advertises an IPv6 destination, but it does not by itself prove that the destination answers correctly over IPv6.
The protocol result comes from the public source address associated with the current HTTPS request. A colon-form address is reported as IPv6 and a dotted address as IPv4. The domain portion separately asks the LumaProbe resolver for public A and AAAA records and returns up to eight of each.
This structure avoids a common misleading claim. Because lumaprobe.com may be reached through a route that differs from another destination, an IPv4 request here does not prove that the device or provider lacks IPv6. Conversely, publishing an AAAA record does not prove that the listed server completes an IPv6 connection.
Run the check on the network you want to understand and note whether a VPN, privacy relay, corporate tunnel or mobile hotspot is active. Those services may select a different protocol or exit network. Enter a public hostname without a path for the DNS portion.
For a controlled comparison, use the same device on another connection, such as home broadband and mobile data. Domain owners should check the exact production hostname because the root domain, www hostname and application subdomains can publish different records.
An IPv6 request confirms that this browser completed the current HTTPS connection over IPv6. IPv4 is still a valid result and does not normally stop modern dual-stack sites from working. If IPv6 is expected but never selected, compare the router, device, VPN and provider documentation.
A returned AAAA record means DNS advertises an IPv6 destination for the entered hostname. A and AAAA together indicate dual-stack publication. AAAA without a working server can cause delays or failures, so site owners should test the actual destination from independent IPv6 networks.
This page does not operate dedicated IPv4-only and IPv6-only test nodes, measure Happy Eyeballs timing or test path-MTU discovery. It reports the real protocol of this request and public DNS data without pretending that those observations are a complete client-readiness certification.
Server-side DNS results can differ from the visitor’s resolver because of caching and geographic routing. A VPN may hide the access network’s protocol. The tool does not expose local addresses, router prefixes or device interface configuration.
If an expected AAAA record is absent, confirm the authoritative DNS configuration and wait for the published TTL after a recent change. If AAAA exists but the site fails on IPv6, verify server routing, firewall rules, TLS virtual hosting and application availability before removing the record.
If the current request remains IPv4, check whether IPv6 is enabled on the router and device and whether the provider offers it. Avoid copying tunnel-broker or DNS settings without understanding their privacy, performance and security effects.
Read the complete LumaProbe test methodology and privacy notes →
No. It shows the protocol used for this request to LumaProbe. Another destination, VPN state or network may select IPv6.
It publishes an IPv6 destination for that hostname. It does not by itself prove that the server, firewall, TLS and application work over IPv6.
No. It reports the real current protocol and public DNS records without claiming to test dedicated IPv6-only reachability, path MTU or every fallback behaviour.