Skip to tool

MIYAIP TOOLS

IPv4/IPv6 Dual-Stack Detection

Run IPv4/IPv6 Dual-Stack Detection from this browser to test each protocol's reachability, public exit address, network identity, response time, and troubleshooting guidance.

IPv4 / IPv6

Protocol reachability is checked directly by the browser

How to Read Dual-Stack Test Results

IPv4 and IPv6 are tested independently against protocol-specific public probes. A protocol is marked available only when this browser actually reaches its probe and the probe returns the public source address it observed.

Dual stack means both paths succeeded, but the addresses, ASN, region, response time, gateway, and route can still differ. IPv4-only and IPv6-only results describe this browser test now; they do not prove every application or destination behaves the same way.

Why IPv6 May Be Unavailable

The ISP may not provide a global IPv6 prefix, the router may not advertise it correctly, or a firewall, VPN, proxy, operating-system policy, browser extension, or temporary probe failure may block the path. A link-local address alone does not establish public IPv6 connectivity.

Retry the failed protocol first, then check the router WAN prefix and gateway, prefix delegation, RA or DHCPv6, outbound firewall rules, and tunnels that may take over only IPv4. Change one layer at a time and retest it independently.

Treat reachability and metadata as separate evidence

Network metadata is requested only after a probe returns a valid public address. If metadata fails, the confirmed connectivity result remains available instead of being overwritten by an enrichment error.

Different IPv4 and IPv6 exits are common and do not by themselves prove a privacy leak. When route consistency matters, compare DNS, WebRTC, VPN, and proxy configuration in addition to the two public network paths.

FAQ

Frequently asked questions

How can I check IPv6 availability in my browser?

Open this page and wait for the IPv6-only public probe. A successful connection confirms that this browser reached the probe over IPv6 for this test; retry failures because routing, firewalls, VPNs, extensions, or temporary probe availability can affect the result.

How does the checker find my public IP?

When the browser connects to a protocol-specific public probe, the probe returns the source address it sees. MiyaIP does not read your private LAN address during this test.

Why can IPv6 be available but slower than IPv4?

Routing, tunnelling, DNS, wireless conditions, or probe distance can affect response time. The page flags IPv6 as noticeably slower only when it is at least 500 ms and three times slower than IPv4 in this run.

Is it normal for IPv4 and IPv6 exits to be different?

Yes. The two protocols can use different gateways, circuits, or autonomous systems. When privacy consistency matters, review DNS, WebRTC, VPN, and proxy configuration as separate evidence.

Does a detection failure mean the network does not have this protocol?

Not necessarily. Temporary probe unavailability, browser extensions, corporate firewalls, and network fluctuations can cause failure. Retry and compare results from other devices before concluding that the protocol is unavailable.

Keep checking

IP and Browser Environment CheckIP Address LookupDNS / NSLookupIP and Domain WHOIS

MIYAIP

Need a stable proxy network that scales?

Create an account to manage proxy products, or review rotating residential proxy pricing first.

Sign up freeView pricing