The IPv6 website test loads any public website twice, once over IPv6 and once over IPv4, and shows whether each one works. Enter a domain or a full URL and you see the DNS records, every redirect, the HTTP status, the certificate and a text preview of the page as it is served over IPv6, so you can check a site even if your own connection has only IPv4.
Runs on our server. The lookups are sent from srvscripts.com, so the result shows what one server in one location sees. Results are cached for up to 5 minutes. Our server is not allowed to test itself, so srvscripts.com shows as "not tested".
Table of Contents
What the test checks
The checker looks up the A and AAAA records of the host, then connects to the IPv6 address and the IPv4 address separately. Each request is pinned to its address family, so an IPv6 test can never quietly fall back to IPv4. For each family you get:
- every request in the chain, following up to 6 redirects, with the status code, response time and the address that answered
- the HTTP version (HTTP/1.1 or HTTP/2) and the certificate subject, issuer and expiry date
- the page title and a short text preview of the page served over IPv6, so you can see that it is the real site and not a default server page
Reading the result
Works over IPv6 and IPv4 means both families reached the same final page. IPv4 only means the domain has no AAAA record. That is common: IPv4 and dual-stack visitors reach the site normally, while visitors on IPv6-only networks depend on their provider offering a translation service such as NAT64 with DNS64. IPv6 failed is the result to act on: the domain announces an IPv6 address but the site does not answer on it, so some visitors on IPv6 networks may see slow loading or errors. Also compare the two final URLs and page titles; a different page over IPv6 usually means the domain is not set up on the server’s IPv6 address and the default page is shown instead.
Fixing IPv6 on a hosting server
In cPanel, add the range in WHM under IPv6 Ranges and then use Assign IPv6 Address for the account. In DirectAdmin, add the IPv6 address to the server, the user and the domain so the web server listens on it. Then allow the web ports over IPv6 in the firewall: in CSF that means IPV6 = “1” and ports 80 and 443 in TCP6_IN. Create the AAAA record at your DNS provider last, after the site answers on the IPv6 address, and run this test again.
If your DNS is hosted elsewhere, such as Cloudflare, the records shown in the control panel’s own DNS editor are not the ones visitors use. Check the live records with the DNS Lookup tool, and test the web ports with the Open Port Checker.
Limits
The test makes plain GET requests to ports 80, 443, 8080 and 8443 of public addresses only, reads at most 512 KB of each page and does not run JavaScript. It does not test from several countries; for that use the Online Ping Test, which can also ping IPv6 addresses.
IPv6 Website Test at a glance
Official documentation: RFC 8200 (IPv6 specification), RFC 3596 (DNS AAAA records), Google IPv6 adoption statistics.
Related tools: What Is My IP Address? · IPv6 Subnet Calculator · TLS Version Checker · CSF Commands Cheat Sheet.
Frequently asked questions
Why does the test say my site is IPv4 only?
The domain has no AAAA record, so dual-stack visitors reach it over IPv4, and visitors on IPv6-only networks reach it only if their network provides a translation service such as NAT64. Add an AAAA record for the server’s IPv6 address at your DNS provider, but only after the web server answers on that address, otherwise IPv6 visitors get errors.
Can I test IPv6 if my own internet has only IPv4?
Yes. The requests are made from our server, which has both IPv4 and IPv6, so your own connection does not matter. To see which address your own device uses, open the What Is My IP tool.
The AAAA record exists but IPv6 fails. What is wrong?
Usually the web server is not listening on the IPv6 address for that domain, the firewall does not allow ports 80 and 443 over IPv6, or the AAAA record points to an old address. Compare the address in the result with the IPv6 address on the server.
Do I need IPv6 on my website?
It is not strictly required. IPv4 and dual-stack visitors reach an IPv4-only site normally, and IPv6-only networks usually offer a translation service such as NAT64 with DNS64, but that depends on the network and is not guaranteed. Adding IPv6 removes that dependency. A broken AAAA record is worse than none, so test it whenever you add or change one.