fortiguard.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 fortiguard.com has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
✗ 2620:101:9005:101::169 no answer
broken
www over IPv6 www.fortiguard.com has no AAAA record.
no
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.
yes
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.
Probes on other continents couldn't connect either, so this isn't only our view.
First measured 2026-11-04; last confirmed 2026-11-04.
What's keeping fortiguard.com from an A
Fix or remove the AAAA record for fortiguard.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.
www.fortiguard.com is an alias of www.fortiguard.com.geo.fortinet.net, which has no IPv6 www.fortiguard.com is a CNAME, so it can't also have its own AAAA record. Ask whoever runs www.fortiguard.com.geo.fortinet.net to enable IPv6 there — or replace the alias with the A and AAAA records they give you. Why some hosts don't offer IPv6
Nameservers without IPv6 ns4.fortinet.com, ns-o1.fortinet.com, ns3.fortinet.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.