This function is currently out of service. Please accept our apologies.
Javascript Required
This site requires Javascript, as well as the ability to pull in cross-site scripts, in order to perform the testing.
If this message does not go away, it means that Javascript has been disabled, either by a plugin or extension in your browser, or by explicit browser setting.
Do you use NoScript?
If you use this Firefox add-on, you'll need to "Temporarilly allow all this page". You will need to do this twice for everything to work. Alternately, disable NoScript entirely until you are done with this site.
You can opt instead to view the simple test, which will give you a quick pass/fail for IPv4, IPv4+IPv6, and IPv6. IT will however offer little diagnostic information.
| Test with IPv4 DNS record |
pending
|
| Test with IPv6 DNS record |
pending
|
| Test if your ISP's DNS server uses IPv6 |
pending
|
| Test with Dual Stack DNS record |
pending
|
| Test IPv4 without DNS |
pending
|
| Test IPv6 without DNS |
pending
|
| Test IPv6 large packet |
pending
|
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 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 ran 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 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 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.
|
This test is based on the IPv6 testing suite by Jason Fesler
