Test your IPv6.

Test with IPv4 DNS record pending -	Fetches an object that has just an A record in DNS. This is expected to use IPv4. IPv6-only users might still reach this, if their provider has employed a NAT64/DNS64 or proxy solution.
Test with IPv6 DNS record pending -	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 with IPv6 DNS record + IPv6 DNS server pending -	Validates that your DNS server is able to reach IPv6-only DNS servers. (Note: This has nothing to do with you using IPv4 or IPv6 to reach the DNS server; only with what happens after you reach your ISP or Corporate DNS server). If this test passes, it means the DNS server ultimately queried, has IPv6 connectivity.
Test with Dual Stack DNS record pending -	Tests a hostname that offers both A and AAAA (IPv4 and IPv6) records. This has nothing to do with whether or not the DNS server has IPv6; any DNS server can look up AAAA records. Instead, this test is to see if your browser can connect to a server that offers both types of addresses. Hopefully, if you have both IPv4 and IPv6 installed, IPv6 is prefered, and connects just as fast. If this test fails or times out, you can expect major problems as publishers start offering their sites on IPv6.
Test IPv4 without DNS pending -	This will try connecting with a literal IPv4 numeric address. This should work for most people, unless they are running IPv6-only. If the first test worked, but this fails, it likely confirms your provider is using NAT64/DNS64; you'll need to only try connecting using hostnames instead of numeric IP addresses.
Test IPv6 without DNS pending -	This will try connecting with a literal IPv6 hexadecimal address. The primary purpose of this test is to separate out your connectivity on IPv6 from your ability to fetch DNS for it.
Test IPv6 large packet pending -	Validate that a request for something bigger than 1500 bytes works. The request itself is > 1500 bytes; and so is the response. In the event that a portion of your IPv6 traffic travels over a tunnel that uses IPv4, and in the event that tunnel sends a packet that is too large, your host won't be properly notified to send/receive smaller packets. This test does not fully test for pmtud issues.

Click to see Statistics

Nothing terribly wrong was detected. However, if you would like to contact me, feel free to fill out this form. I'll get a copy of your test results along with whatever other information you're willing to offer.

All fields are optional; but the more information you are willing to provide, the better I can both make this web site as well as better understand the challenges ahead for the world to move to IPv6.

Thanks,
Jason Fesler <jfesler@gigo.com>

Contact info (email, Y!IM, jabber, freenode IRC id) if you'll permit me to contact you.

Are you willing to be contacted by help I recruit from other ISP's? See our helpers page for more details, and privacy policy associated with doing so. By saying no, your comments will be restricted to just Jason Fesler (who will respond on an as-available basis).

Any information you think I might find useful (what router you're using, or a firewall in the way, or type of proxy you use, etc). This includes general feedback.

If you are technically minded please cut/paste the output of netstat -nr and ifconfig -a in the box below.

If you are technically minded please cut/paste the output of

ip -f inet6 route
                        show

and ip -f inet6 addr in the box below.

If you are technically minded, please open a "Command Prompt" or "cmd" window, and paste the output of ipconfig /all, netsh interface ipv6 show teredo, and netsh interface ipv6 show route in the box below.

Test with IPv4 DNS record		pending
Test with IPv6 DNS record		pending
Test with IPv6 DNS record + IPv6 DNS server		pending
Test with Dual Stack DNS record		pending
Test IPv4 without DNS		pending
Test IPv6 without DNS		pending
Test IPv6 large packet		pending

Test your IPv6 connectivity.