Bonjour,
voici les détails (désolé, ils sont en anglais)
Test with IPv4 DNS record
ok (0.890s) using ipv4
Test with IPv6 DNS record
timeout (15.010s)
Test with Dual Stack DNS record
ok (1.174s) using ipv4
Test for Dual Stack DNS and large packet
ok (1.115s) using ipv4
Test IPv6 large packet
timeout (15.011s)
Test if your ISP's DNS server uses IPv6
ok (1.539s) using ipv4
Find IPv4 Service Provider
ok (0.929s) using ipv4 ASN 12322
Find IPv6 Service Provider
ok (0.571s) using ipv6 ASN 12322
Test with IPv6 DNS record
timeout (15.010s)
https://ipv6.vm3.test-ipv6.com/ip/?callback=?Fetches an object that has just an AAAA record in DNS. This is expected to use IPv6. Users not yet on the IPv6 Internet are likely to see this fail. As long as it fails quickly, it will be OK - for now.
Test IPv6 large packet
timeout (15.011s)
https://mtu1280.vm3.test-ipv6.com/ip/?callback=?&size=1600&fill=xxx...xxxValidates that IPv6 requests with large packets work. If this test times out, but other IPv6 tests work, it suggests that there may be PMTUD issues; possibly involving IP tunnels. Double check to make sure that ICMPv6 Type 2 ("Packet Too Big") messages are not filtered by your firewall.
et le resultat du ping par le site subnetonline
IPv6 Ping Output:
PING ipv6.google.com(muc12s04-in-x0e.1e100.net (2a00:1450:4016:803::200e)) 32 data bytes
40 bytes from muc12s04-in-x0e.1e100.net (2a00:1450:4016:803::200e): icmp_seq=1 ttl=57 time=19.0 ms
40 bytes from muc12s04-in-x0e.1e100.net (2a00:1450:4016:803::200e): icmp_seq=2 ttl=57 time=18.9 ms
40 bytes from muc12s04-in-x0e.1e100.net (2a00:1450:4016:803::200e): icmp_seq=3 ttl=57 time=18.9 ms
40 bytes from muc12s04-in-x0e.1e100.net (2a00:1450:4016:803::200e): icmp_seq=4 ttl=57 time=19.0 ms
--- ipv6.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 18.946/18.997/19.024/0.171 ms