fortiguard.com
IPv6
Measured 2026-11-15 17:08 UTC · aaaa.botPublishes an IPv6 address that does not answer.
Connections on 443 and 80 got no answer, and probes on other continents agree.
Probes on other continents could not connect either, so this is not only our view.
- ✗ fortiguard.com: published, no answer (0 of 1)
- ✗ www.fortiguard.com: no IPv6 address
- ✓ Mail: has IPv6
- ✗ Nameservers: none have IPv6
Details: published addresses and what answered
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| fortiguard.com | Published2620:101:9005:101::169 | Answers when we connect✗ no answer on 443 or 80 |
| www.fortiguard.com | Publishedno IPv6 address published | Answers when we connectnothing to test |
PublishedNo MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record. | Answers when we connecthas IPv6 | |
| Nameservers | Publishedns4.fortinet.comns-o1.fortinet.comns3.fortinet.com | Answers when we connect✗ no IPv6✗ no IPv6✗ no IPv6 |
See where it lives on the IPv4 map →
Lineage
Our records: Oct 18, 2013 → Nov 15, 2026Oldest registry snapshot we hold: 2013 · 3 renewals on record · DNS at fortinet.com · 2 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
Registrar
- Network Solutions, LLCFeb 2019 – Nov 2021
- MarkMonitor, Inc.last seen Apr 2026Dec 2021 – Apr 2026
DNS provider
- fortinet.comNOWSeen from Oct 2013
IPv6
- IPv6published, but not answeringFirst measured Nov 2026
What changed
- IPv6 first measured: published, but not answering on Nov 4, 2026fortiguard.com has 1 IPv6 address. Grade F. Measured by aaaa.bot, 2026-11-04 16:22 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- Renewed +2 years between Mar 2, 2026 and Apr 12, 2026Expiry moved from 2026-05-09 to 2028-05-09, at MarkMonitor, Inc.
- New nameservers at fortinet.com between Jun 8, 2025 and Jun 14, 2025ns2.fortinet.com, ns3.fortinet.com, ns4.fortinet.com → ns-o1.fortinet.com, ns3.fortinet.com, ns4.fortinet.com. Old set last seen in WHOIS on 2025-06-08; new set first seen in WHOIS on 2025-06-14.
- New nameservers at fortinet.com between Feb 1, 2024 and Feb 20, 2024ns1.fortinet.com, ns2.fortinet.com, ns3.fortinet.com → ns2.fortinet.com, ns3.fortinet.com, ns4.fortinet.com. Old set last seen in WHOIS on 2024-02-01; new set first seen in WHOIS on 2024-02-20.
- Moved to MarkMonitor, Inc between Nov 25, 2021 and Dec 21, 2021From Network Solutions, LLC to MarkMonitor, Inc, with 2 years added. Expiry moved from 2024-05-09 to 2026-05-09.
- Renewed +5 years between Feb 23, 2019 and Mar 26, 2019Expiry moved from 2019-05-09 to 2024-05-09, at Network Solutions, LLC.
Solid bar: the stretch we observed that name. Dot: a single sighting. Dotted line: no record between sightings of the same name. Nothing is drawn between different names.
Registrar and renewals: 166 WHOIS/RDAP snapshots, 2013-11-24 to 2026-05-31 (ledger built 2026-09-27). Every renewal
DNS provider, registry zone files: 120 .com zone-file snapshots held, 2013-10-18 to 2026-11-15.
DNS provider, WHOIS snapshots: 138 WHOIS/RDAP snapshots that listed nameservers, 2013-11-24 to 2026-05-31 (who.is archive). Both sources feed one row per provider (hover a bar to see which); a change is placed between the nearest observations on either side, and where the two sources disagree, both are listed under What changed.
Want to know when fortiguard.com changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2003 — the same year as googlevideo.com, wordpress.org and skype.com.