googleppcservice.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 googleppcservice.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2a07:7800::162 no answer
broken
www over IPv6 www.googleppcservice.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2a07:7800::162 no answer
broken
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record.
mx.stackmail.com ✗
no
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.
Fix or remove the AAAA record for googleppcservice.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.googleppcservice.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 mx.stackmail.com has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.
Nameservers without IPv6 ns1.mydnscp.com, ns4.mydnscp.com, ns3.mydnscp.com, ns2.mydnscp.com all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.