Domain Intelligence Report
IPv6
Measured 2026-11-01 14:50 UTC · aaaa.botA
Website, mail and DNS all work over IPv6.
Both published IPv6 addresses accepted a connection when we tried them.
- ✓ about.com answers (2 of 2 addresses)
- ✓ Mail: 5 of 5 servers have IPv6
- ✓ Nameservers: 3 of 3 have IPv6
Details: published addresses and what answered
Loads over IPv6 with a valid certificate after 2 redirects: HTTP 200.
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| about.com | Published2606:4700:7::1d82a06:98c1:58::1d8 | Answers when we connect✓ answers on 443✓ answers on 443 |
Publishedaspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.com | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6 | |
| Nameservers | Publishedblue.foundationdns.comblue.foundationdns.netblue.foundationdns.org | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6 |
First measured with IPv6 on 2026-11-01Changes are recorded from here on, each with its date.
Lineage
Our records: May 11, 2007 → Nov 1, 2026Oldest registry snapshot we hold: 2007 · 6 renewals on record · DNS at Cloudflare Foundation DNS · 6 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
Registrar
2,262 snapshots
MarkMonitor, Inc.Renewed +6 yearsbetween Jul 31, 2011 and Aug 1, 2011Expiry moved from 2014-03-12 to 2020-03-12, at CORPORATE DOMAINS, INC.Moved to MarkMonitor, Incbetween Nov 14, 2017 and Nov 21, 2017From CSC CORPORATE DOMAINS, INC to MarkMonitor, Inc, with 2 years added. Expiry moved from 2020-03-12 to 2022-03-11.Renewed +2 yearsbetween Feb 2, 2022 and Feb 16, 2022Expiry moved from 2022-03-12 to 2024-03-12, at MarkMonitor, Inc.Renewed +1 yearbetween Jan 17, 2024 and Feb 10, 2024Expiry moved from 2024-03-12 to 2025-03-12, at MarkMonitor, Inc.Renewed +1 yearbetween Feb 6, 2025 and Feb 21, 2025Expiry moved from 2025-03-12 to 2026-03-12, at MarkMonitor, Inc.Renewed +1 yearbetween Jan 18, 2026 and Feb 17, 2026Expiry moved from 2026-03-12 to 2027-03-12, at MarkMonitor, Inc.
Nameservers
registry zone files
DNS moved to Oracle Dynbetween Mar 27, 2015 and Sep 23, 2015nydns1.about.com, nydns2.about.com, sjdns1.about.com, sjdns2.about.com, txdns1.about.com, txdns2.about.com → ns1.p30.dynect.net, ns2.p30.dynect.net, ns3.p30.dynect.net, ns4.p30.dynect.net.
seen in WHOIS
NS1 + Oracle DynNS1 + icsn.comDNS moved to NS1between Oct 17, 2016 and Oct 21, 2016ns1.p30.dynect.net, ns2.p30.dynect.net, ns3.p30.dynect.net, ns4.p30.dynect.net → dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net. Old set last seen in WHOIS on 2016-10-17; new set first seen in WHOIS on 2016-10-21.DNS moved to NS1 + Oracle Dynbetween Oct 27, 2016 and Oct 30, 2016dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net → dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns1.p30.dynect.net, ns2.p30.dynect.net, ns3.p30.dynect.net, ns4.p30.dynect.net. Old set last seen in WHOIS on 2016-10-27; new set first seen in WHOIS on 2016-10-30.DNS moved to NS1between Aug 22, 2019 and Aug 27, 2019dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns1.p30.dynect.net, ns2.p30.dynect.net, ns3.p30.dynect.net, ns4.p30.dynect.net → dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net. Old set last seen in WHOIS on 2019-08-22; new set first seen in WHOIS on 2019-08-27.DNS moved to NS1 + icsn.combetween Sep 3, 2019 and Sep 9, 2019dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net → dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns01.icsn.com, ns02.icsn.com, ns03.icsn.com, ns04.icsn.com. Old set last seen in WHOIS on 2019-09-03; new set first seen in WHOIS on 2019-09-09.DNS moved to Cloudflare Foundation DNSbetween Aug 22, 2025 and Sep 17, 2025dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns01.icsn.com, ns02.icsn.com, ns03.icsn.com, ns04.icsn.com → blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org. Old set last seen in WHOIS on 2025-08-22; new set first seen in WHOIS on 2025-09-17.
IPv6
aaaa.bot check
2011201520192026
What changed (latest 8 of 13)
- IPv6 first measured: published, and answering on Nov 1, 2026about.com has 2 IPv6 addresses. Grade A. Measured by aaaa.bot, 2026-11-01 14:50 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- Renewed +1 year between Jan 18, 2026 and Feb 17, 2026Expiry moved from 2026-03-12 to 2027-03-12, at MarkMonitor, Inc.
- DNS moved to Cloudflare Foundation DNS between Aug 22, 2025 and Sep 17, 2025dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns01.icsn.com, ns02.icsn.com, ns03.icsn.com, ns04.icsn.com → blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org. Old set last seen in WHOIS on 2025-08-22; new set first seen in WHOIS on 2025-09-17.
- Renewed +1 year between Feb 6, 2025 and Feb 21, 2025Expiry moved from 2025-03-12 to 2026-03-12, at MarkMonitor, Inc.
- Renewed +1 year between Jan 17, 2024 and Feb 10, 2024Expiry moved from 2024-03-12 to 2025-03-12, at MarkMonitor, Inc.
- Renewed +2 years between Feb 2, 2022 and Feb 16, 2022Expiry moved from 2022-03-12 to 2024-03-12, at MarkMonitor, Inc.
- DNS moved to NS1 + icsn.com between Sep 3, 2019 and Sep 9, 2019dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net → dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns01.icsn.com, ns02.icsn.com, ns03.icsn.com, ns04.icsn.com. Old set last seen in WHOIS on 2019-09-03; new set first seen in WHOIS on 2019-09-09.
- DNS moved to NS1 between Aug 22, 2019 and Aug 27, 2019dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net, ns1.p30.dynect.net, ns2.p30.dynect.net, ns3.p30.dynect.net, ns4.p30.dynect.net → dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net. Old set last seen in WHOIS on 2019-08-22; new set first seen in WHOIS on 2019-08-27.
Registrar and renewals: 2,262 WHOIS/RDAP snapshots, 2007-05-11 to 2026-05-17 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 106 .com zone-file snapshots held, 2013-10-18 to 2026-11-01.
Nameservers, WHOIS snapshots: 586 WHOIS/RDAP snapshots that listed nameservers, 2011-07-06 to 2026-06-18 (who.is archive). A change is placed between the nearest observations on either side, from whichever source made them; where the two sources disagree, both are shown.
Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.
Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.
Gathering intelligence... (0/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
Checking…no attacks or spoofing
Up
Checking…reachable and responding
Right
Set up Page Watchit is what it is
Ready
Checking…you see what's coming
Outline
Gathering data — check results will appear here as they complete.
DNS Records
WHOIS
Then vs Nownew
DetailsNot enough evidence to say whether this is still the same organisation.
Now: News or media · maintained
AI-judged Sep 30, 2026: likely, not verified
SSL/TLS
Security
Email Auth
DNSSEC
Tech Stack
HTTP / Headers
Threats
Zone census
Subdomains
Web Archive
Deliverability
Want to know when about.com changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.