INTERNET PROTOCOL
IPv4
Connecting to IPv4-only public network probe.
- Public IP
- —
- network belonging
- —
- Country/Region
- —
- Browser response
- —
- Detection time
- —
technical details
- detection probe
- IPv4 Probe A
- HTTP status
- —
- failure stage
- —
- Observation time
- —
MiyaIP connection diagnostics
IPv4 / IPv6 Connectivity Test
See which network paths your browser can reach
Connect to the IPv4 and IPv6 public network probes from the current browser to independently verify reachability, egress address, and response time. The page is automatically detected after opening and does not read the device's internal network address.
The detection results are only saved in the current browser; network ownership query is completed through the MiyaIP backend.
IPv4 and IPv6 connection detection results
Detecting
Checking IPv4 and IPv6 separately
The two protocols are independent of each other and results are displayed immediately upon completion of each.
IPv4In preparation
IPv6In preparation
Under detection
INTERNET PROTOCOL
IPv6
Connecting to IPv6-only public network probe.
- Public IP
- —
- network belonging
- —
- Country/Region
- —
- Browser response
- —
- Detection time
- —
technical details
- detection probe
- IPv6 Probe A/B
- HTTP status
- —
- failure stage
- —
- Observation time
- —
Only save in this browser
Last 10 tests
After completing the dual-protocol detection, the summary results will be displayed here.
How to understand the results
Dual stack means two independent connections
Only when the browser actually connects to the public network target of the corresponding protocol will it be marked as "available". System preferences, DNS policies, and route quality can all cause two paths to behave differently.
Dual stack available
Both IPv4 and IPv6 are successful. Modern browsers usually choose the faster one through Happy Eyeballs, and there is no guarantee that every website will use the same protocol.
IPv4 only
This is a common situation at present. It may be that the operator, optical modem, router or device has not obtained available IPv6 configuration, or it may be that the firewall is blocking IPv6.
IPv6 only
It is less common in public network environments and may rely on NAT64 / DNS64 to access IPv4 content. If some old services cannot be opened, the conversion gateway and DNS should be checked.
Exit paths are different
IPv4 has a different ASN or region than IPv6, possibly from offloading, enterprise policy, or carrier routing. It does not in itself amount to a privacy leak.
Connection troubleshooting
When IPv6 is unavailable, start with these three places
A failure could also result from a brief network fluctuation. Re-detect first, and then confirm layer by layer according to the connection link.
- 01
Confirm whether the operator issues IPv6
Check the router WAN status to see if you have obtained the global IPv6 prefix and gateway; only the link-local address does not mean that public IPv6 is available.
- 02
Check router and terminal settings
Enable IPv6, prefix delegation, and RA/DHCPv6 if necessary; avoid setting IPv6 firewalls to completely block outbound connections.
- 03
Exclude VPNs, proxies, and security software
Temporarily disable tunnels that may only take over IPv4 and try again. If the dual egress ASNs are different, you should also check whether protocol offloading is configured.
FAQ
About IPv4/IPv6 detection
Why can the public IP be found on the page?
When a browser accesses a public network probe isolated by protocol, the probe returns the source address it sees. MiyaIP will not read your LAN address through this.
Why does IPv6 appear to be available but slower than IPv4?
May be related to bypass routing, tunneling, DNS, wireless fluctuations or probe distance. Only when IPv6 is at least 500 ms slower this time and reaches 3 times that of IPv4, the page will prompt that it is obviously slow.
Is it normal that IPv4 and IPv6 egress are different?
Normal. The two protocols can be carried by different gateways, circuits or autonomous systems. When privacy consistency is required, special checks can be made based on DNS, WebRTC, and proxy configuration.
Does the detection failure mean that the network does not have this protocol?
Not necessarily. Temporary unreachability of the probe, browser extensions, corporate firewalls, and network jitters may cause failure, and should be judged based on retry and other device results.
continue diagnosis