Test your IPv6.

How this test works: Your browser will be instructed to reach a series of URLs. The combination of successes and failures tells a story about how ready you are for when publishers start offering their web sites on 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 Dual Stack DNS record pending -	This is the most important test. This verifies your browser can connect to a site that has both IPv4 and IPv6 records published. IPv4 only hosts should connect fine (using IPv4). If this test fails or times out, you can expect major problems as publishers start offering their sites on IPv6.
Test for Dual Stack DNS and large packet pending -	Validates that you can connect to a dual-stack server (like the ds test); and that you can send/receive large packets on that connection. If this test times out for any reason, it indicates trouble for World IPv6 Day.
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. A secondary purpose is to see if you have Teredo enabled; some systems may only use Teredo when an IPv6 address is in the URL.
Test IPv6 large packet pending -	Validates 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.
Test if your ISP's DNS server uses IPv6 pending - (This is bonus credit)	This is a test of your ISP's resolver (instead of a test of your host). If this test passes, your DNS server (often run by your ISP) is capable of reaching IPV6-only DNS authoritative servers on the Internet. This is not critical (at this time) for you to reach sites via IPv6.
Test for buggy DNS pending -	Queries for a malformed AAAA record. Some routers mishandle these as "A" records, and only keep the first 32 bits. We want this test to fail to connect.

If the summary results indicated problems, you (or your technical support) may be able to use the information above to diagnose the issues. Each of the test urls and their results is shown on the left side. To the right you'll see a description of what that URL was designed to test.

After each test is ran. The summary page attempts to look at the results If the summary doesn't seem to make sense given the symptoms recorded above, or if you need further assistance, please feel free to contact us.

Click to see Share Results / Contact

This form will let you leave a comment, voice concerns, or ask questions. Your test results will be included automatically.

Please leave your comments using English, if possible.

There may be a delay for a response, due to recent press releases about World IPv6 Day.

If reporting a problem with the test, or requesting help with your results, please fill out all requested information to the best of your ability. If leaving general comments, use your best judgement on how much to report.

Thanks,
Jason Fesler <jfesler@test-ipv6.com>

Purpose for comment:

Email address if you'll permit me to contact you. Required, if you wish a response.

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 the following commands:
netstat -nr
ifconfig -a
Copy the output from those commands, into the box below. This will help me confirm/deny any theories relating to your question.

If you are technically minded please cut/paste the output of the following commands:
ip -f inet6 route show
ip -f inet6 addr
Copy the output from those commands, into the box below. This will help me confirm/deny any theories relating to your question.

If you are technically minded, please open a "Command Prompt" or "cmd" window, and run these three commands:
ipconfig /all
netsh interface ipv6 show teredo
netsh interface ipv6 show route
Copy the output from those commands, into the box below. This will help me confirm/deny any theories relating to your question.

Test with IPv4 DNS record		pending
Test with IPv6 DNS record		pending
Test with Dual Stack DNS record		pending
Test for Dual Stack DNS and large packet		pending
Test IPv4 without DNS		pending
Test IPv6 without DNS		pending
Test IPv6 large packet		pending
Test if your ISP's DNS server uses IPv6		pending
Test for buggy DNS		pending

Test your IPv6 connectivity.