What it means
Your website has an AAAA record, but when we connected to that IPv6 address the connection failed or timed out, while the same site answered over IPv4.
Why it matters
This is worse than having no IPv6 at all. Browsers and operating systems on IPv6 networks usually try the IPv6 address first. When it doesn't answer they wait, then fall back to IPv4, so visitors see a slow first load or an error. Some clients, such as scripts and older devices, don't fall back at all.
How to fix it
- Use the DNS lookup to see the AAAA records for the domain and www. An address left over from an old server or an old host is the most common cause; if so, remove the record or replace it.
- On the server, check that the address is configured on the network interface and that the web server listens on IPv6 as well as IPv4.
- Check the server's firewall and your provider's security groups: IPv6 rules are separate from IPv4 rules and are often missing for ports 80 and 443.
- If you can't fix it quickly, remove the AAAA record. Visitors then use IPv4 straight away.
Check it worked
Run the IPv6 test again. The website row should say it answers over IPv6 the same as over IPv4, or show no IPv6 address if you removed the record.