166.com
IPv6
Measured 2026-11-01 05:14 UTC · aaaa.botThe website has no IPv6.
166.com has no IPv6 address published.
- ✗ 166.com: no IPv6 address
- ✗ www.166.com: no IPv6 address
- ✗ Mail: 0 of 0 servers have IPv6
- ✗ Nameservers: none have IPv6
Details: published addresses and what answered
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| 166.com | Publishedno IPv6 address published | Answers when we connectnothing to test |
| www.166.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 no AAAA record. | Answers when we connectsee detail | |
| Nameservers | Publishedns5.166.comns2.166.comns6.166.comns8.166.comns4.166.comns1.166.comns3.166.com | Answers when we connect✗ no IPv6✗ no IPv6✗ no IPv6✗ no IPv6✗ no IPv6✗ no IPv6✗ no IPv6 |
Lineage
Our records: Jul 5, 2011 → Nov 1, 2026Oldest registry snapshot we hold: 2011 · 6 renewals on record · DNS at 166.com · 1 nameserver change seen. These dates are when our records begin, not when the domain was registered.
What changed
- IPv6 first measured: no IPv6 published on Nov 1, 2026166.com: no IPv6 published. Grade D. Measured by aaaa.bot, 2026-11-01 05:14 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- Renewed +2 years between Jan 13, 2026 and Feb 13, 2026Expiry moved from 2026-03-10 to 2028-03-10, at MarkMonitor Information Technology (Shanghai) Co., Ltd.
- Moved to MarkMonitor Information Technology (Shanghai) Co., Ltd between Sep 14, 2023 and Sep 20, 2023From MarkMonitor, Inc to MarkMonitor Information Technology (Shanghai) Co., Ltd, with 1 year added. Expiry moved from 2025-03-10 to 2026-03-10.
- Renewed +2 years between Jan 25, 2023 and Feb 28, 2023Expiry moved from 2023-03-09 to 2025-03-10, at MarkMonitor, Inc.
- Renewed +2 years between Jan 27, 2021 and Feb 17, 2021Expiry moved from 2021-03-09 to 2023-03-09, at MarkMonitor, Inc.
- Renewed +2 years between Jan 3, 2019 and Feb 16, 2019Expiry moved from 2019-03-09 to 2021-03-09, at MarkMonitor, Inc.
- DNS moved to 166.com between Jun 22, 2017 and Aug 21, 2017ns1.nease.net, ns2.nease.net, ns3.nease.net, ns4.nease.net → ns1.166.com, ns2.166.com, ns3.166.com, ns4.166.com, ns5.166.com, ns6.166.com, ns8.166.com. Old set last seen in WHOIS on 2017-06-22; new set first seen in WHOIS on 2017-08-21.
- Moved to MarkMonitor, Inc between Sep 14, 2011 and Oct 14, 2011From NETWORK SOLUTIONS, LLC to MarkMonitor, Inc, with 5 years added. Expiry moved from 2014-03-10 to 2019-03-10.
Registrar and renewals: 209 WHOIS/RDAP snapshots, 2011-07-05 to 2026-05-31 (ledger built 2026-09-27). Every renewal
Nameservers, registry zone files: 105 .com zone-file snapshots held, 2013-10-18 to 2026-10-31.
Nameservers, WHOIS snapshots: 210 WHOIS/RDAP snapshots that listed nameservers, 2011-07-05 to 2026-06-28 (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.
Want to know when 166.com changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.