Fail

Your site answers over IPv4 but not over IPv6

The short version

Fix IPv6 on the server or remove the AAAA record until it works.

What it means

Your site answers on its IPv4 addresses, but none of its IPv6 addresses answer on port 80 or 443. The domain has AAAA records, so devices on IPv6 networks are told to use them, and those connections fail.

Why it matters

Phones on many mobile networks and a large share of home connections prefer IPv6. Their browsers try the IPv6 address first and wait for it to fail before falling back to IPv4, which makes your site slow to open, or unreachable for clients that don't fall back. A broken IPv6 address is worse than none at all.

How to fix it

  1. Use the DNS lookup to see the AAAA records. If one points at an old server or a host you no longer use, remove it or replace it with the current address.
  2. On the server, check that the IPv6 address is configured on the network interface, and that the web server listens on IPv6 as well as IPv4 (for nginx, listen [::]:443 ssl; and listen [::]:80;).
  3. Check the firewall: IPv6 rules are separate from IPv4 rules (ip6tables, or the IPv6 part of your provider's security group) and are often missing.
  4. If you can't fix it soon, remove the AAAA records so visitors use IPv4 straight away, and add them back once IPv6 works.

Check it worked

Run the web port check again with the fresh option: the IPv6 rows should show ports open. The IPv6 test also checks that the site serves the same page over IPv6.