667.com - dns.ninja

667.com

DNSSEC⚠️ Not signed
NSns1.dns.com ⚠️ Not in zone NS records
A2001:df2:f080:2::1:1πŸ‡­πŸ‡° HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED
A154.23.191.128πŸ‡ΊπŸ‡Έ HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED
A154.86.21.128πŸ‡­πŸ‡° HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED
NSns2.dns.com ⚠️ Not in zone NS records
A2001:df2:f080:2::1:2πŸ‡­πŸ‡° HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED
A154.23.191.129πŸ‡ΊπŸ‡Έ HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED
A154.86.21.129πŸ‡­πŸ‡° HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED

com

Same first word

Similar names

DNS History

12 records (2 active, 10 former)

20162017201820192020202120222023202420252026NSns1.dns.comns2.dns.comlara.ns.cloudflare.comns3.dnsdun.comns3.dnsdun.netwoz.ns.cloudflare.comMXmail.667.comA104.28.10.58104.28.11.582400:cb00:2048:1::681c:a3a2400:cb00:2048:1::681c:b3aCNAMEtyc2018.admincdn.com
β—‹NSlara.ns.cloudflare.com2015-07-21 β†’ 2017-02-11 Β· 4 obs
● 2015-07-21 10:20:18
● 2017-02-11 07:10:44
β—‹ 2018-11-29 23:23:30
β—‹ 2026-07-04 14:58:02
●NSns1.dns.com2026-03-06 β†’ 2026-07-04 Β· 3 obs
β—‹ 2018-11-29 23:23:30
● 2026-03-06 05:17:14
● 2026-07-04 14:58:02
●NSns2.dns.com2026-03-06 β†’ 2026-07-04 Β· 3 obs
β—‹ 2018-11-29 23:23:30
● 2026-03-06 05:17:14
● 2026-07-04 14:58:02
β—‹NSns3.dnsdun.com2018-11-29 β†’ 2018-11-29 Β· 4 obs
β—‹ 2017-02-11 07:10:44
● 2018-11-29 23:23:30
β—‹ 2026-03-06 05:17:14
β—‹ 2026-07-04 14:58:02
β—‹NSns3.dnsdun.net2018-11-29 β†’ 2018-11-29 Β· 4 obs
β—‹ 2017-02-11 07:10:44
● 2018-11-29 23:23:30
β—‹ 2026-03-06 05:17:14
β—‹ 2026-07-04 14:58:02
β—‹NSwoz.ns.cloudflare.com2015-07-21 β†’ 2017-02-11 Β· 4 obs
● 2015-07-21 10:20:18
● 2017-02-11 07:10:44
β—‹ 2018-11-29 23:23:30
β—‹ 2026-07-04 14:58:02
β—‹MXmail.667.com2015-07-21 β†’ 2017-02-11 Β· 4 obs
● 2015-07-21 10:20:18
● 2017-02-11 07:10:44
β—‹ 2018-11-29 23:23:30
β—‹ 2026-07-04 14:58:02
β—‹A104.28.10.582015-07-21 β†’ 2017-02-11 Β· 4 obs
● 2015-07-21 10:20:18
● 2017-02-11 07:10:44
β—‹ 2018-11-29 23:23:30
β—‹ 2026-07-04 14:58:02
β—‹A104.28.11.582015-07-21 β†’ 2017-02-11 Β· 4 obs
● 2015-07-21 10:20:18
● 2017-02-11 07:10:44
β—‹ 2018-11-29 23:23:30
β—‹ 2026-07-04 14:58:02
β—‹A2400:cb00:2048:1::681c:a3a2017-02-11 β†’ 2017-02-11 Β· 4 obs
β—‹ 2015-07-21 10:20:18
● 2017-02-11 07:10:44
β—‹ 2018-11-29 23:23:30
β—‹ 2026-07-04 14:58:02
β—‹A2400:cb00:2048:1::681c:b3a2017-02-11 β†’ 2017-02-11 Β· 4 obs
β—‹ 2015-07-21 10:20:18
● 2017-02-11 07:10:44
β—‹ 2018-11-29 23:23:30
β—‹ 2026-07-04 14:58:02
β—‹CNAMEtyc2018.admincdn.com2018-11-29 β†’ 2018-11-29 Β· 3 obs
● 2018-11-29 23:23:30
β—‹ 2026-03-06 05:17:14
β—‹ 2026-07-04 14:58:02

πŸ” DNS Trace

Analysis

Name Servers

The NS records for 667.com delegate to ns1.dns.com and ns2.dns.com.

The name server configuration of 667.com is shared with other domains, for instance xameijing.com, 2du11.com, 56787wx.com and two others.

667.com and other domains like 2621.org share at least a portion of their name servers.

ns1.dns.com points to 154.23.191.128, 154.86.21.128 and 2001:df2:f080:2::1:1. ns2.dns.com points to 154.23.191.129, 154.86.21.129 and 2001:df2:f080:2::1:2. Both hosts resolve to three IP numbers.