xn--via-lndle-z2a.com publishes IPv6 but doesn't answer on it.
Has both IPv4 (A) and IPv6 (AAAA) addresses.
F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6 xn--via-lndle-z2a.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2a00:1158:0:100::14 no answer
broken
www over IPv6 www.xn--via-lndle-z2a.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2a00:1158:0:100::14 no answer
broken
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record.
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns59.domaincontrol.com ✓ns60.domaincontrol.com ✓
yes
What's keeping xn--via-lndle-z2a.com from an A
Fix or remove the AAAA record for xn--via-lndle-z2a.com Something published an IPv6 address but nothing answers on it, so IPv6 visitors wait for a timeout first. Either make the server listen on IPv6 (and allow ports 443/80 through its firewall), or delete the AAAA record until it does.
Fix or remove the AAAA record for www.xn--via-lndle-z2a.com Something published an IPv6 address but nothing answers on it, so IPv6 visitors wait for a timeout first. Either make the server listen on IPv6 (and allow ports 443/80 through its firewall), or delete the AAAA record until it does.
Mail servers without IPv6 smtp.secureserver.net, mailstore1.secureserver.net have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.