What it means
Your website answers over IPv6 and over IPv4, but not in the same way: the status code differs, for example an error over IPv6 and a page over IPv4, or both return a page but with different titles.
Why it matters
Visitors on IPv6 networks see something different from everyone else, and you may never notice because your own connection uses IPv4. Typical causes are an AAAA record that points at an old server, a default page on a load balancer whose IPv6 side isn't set up, or a server block that is configured only for IPv4.
How to fix it
- Compare the A and AAAA records with the DNS lookup. If they point at different hosts or providers, the AAAA record is probably stale; update or remove it.
- On the server, make sure the site's configuration covers both families. In nginx, every
listen 443needs a matchinglisten [::]:443; in Apache, check that the virtual host isn't bound to an IPv4 address only. - On a CDN or load balancer, check that the IPv6 listener sends traffic to the same backend as the IPv4 one.
- Test from an IPv6 connection, for example
curl -6 -I https://example.com/, and compare withcurl -4.
Check it worked
Run the IPv6 test again. The website row should say it answers over IPv6 the same as over IPv4.