chroniclyme.com - robtex.com
chroniclyme.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.trafficclub.com ⚠️ Not in zone NS records | ||||||
| A | 104.26.12.156Cloudflare104.26.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 104.26.13.156Cloudflare104.26.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 172.67.69.165🇺🇸 Cloudflare172.67.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.trafficclub.com ⚠️ Not in zone NS records | ||||||
| A | 104.26.12.156Cloudflare104.26.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 104.26.13.156Cloudflare104.26.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 172.67.69.165🇺🇸 Cloudflare172.67.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774484167 | ||||||
Same first word
chroniclyme.com |
chroniclyme.org |
DNS History
9 records (2 active, 7 former)
○NSns1.ndsplitter.com2016-01-13 → 2016-08-12 · 4 obs
● 2016-08-12 15:04:02
○ 2017-04-01 22:10:46
○ 2026-03-26 00:21:18
●NSns1.trafficclub.com2017-04-01 → 2026-03-26 · 3 obs
● 2017-04-01 22:10:46
● 2026-03-26 00:21:18
○NSns2.ndsplitter.com2016-01-13 → 2016-08-12 · 4 obs
● 2016-08-12 15:04:02
○ 2017-04-01 22:10:46
○ 2026-03-26 00:21:18
●NSns2.trafficclub.com2017-04-01 → 2026-03-26 · 3 obs
● 2017-04-01 22:10:46
● 2026-03-26 00:21:18
○NSns3.ndsplitter.com2016-01-13 → 2016-08-12 · 4 obs
● 2016-08-12 15:04:02
○ 2017-04-01 22:10:46
○ 2026-03-26 00:21:18
○NSns3.trafficclub.com2017-04-01 → 2017-04-01 · 4 obs
● 2017-04-01 22:10:46
○ 2026-03-16 20:56:46
○ 2026-03-26 00:21:18
○A144.76.0.2422016-04-06 → 2017-04-01 · 5 obs
● 2016-04-06 06:28:40
● 2017-04-01 22:10:46
○ 2026-03-16 20:56:46
○ 2026-03-26 00:21:18
○A144.76.1.1302016-04-06 → 2017-04-01 · 5 obs
● 2016-04-06 06:28:40
● 2017-04-01 22:10:46
○ 2026-03-16 20:56:46
○ 2026-03-26 00:21:18
○A78.46.179.1342016-01-13 → 2016-01-13 · 3 obs
○ 2016-04-06 06:28:40
○ 2026-03-26 00:21:18
🔍 DNS Trace
Analysis
Name Servers
chroniclyme.com is delegated to two name servers: ns1.trafficclub.com and ns2.trafficclub.com.
chroniclyme.com uses the same name server setup as other domains, for instance tamildvds.com, mortgagewalker.com, floridataxis.com, watchpicks.com and maxin.com.
chroniclyme.com shares name servers with other domains at least partially, for instance careerskills101.com, sciencespring.com, goldclubdating.net, swisscanteen.com and jiffynote.com.
These name servers are commonly used with ns3.trafficclub.com, ns4.trafficclub.com, ns919.0assion.com.2018-08-29.nsdns.info and ns920.0assion.com.2018-08-29.nsdns.info.
Host names with three IP numbers:
ns1.trafficclub.com points to 104.26.12.156, 104.26.13.156 and 172.67.69.165; ns2.trafficclub.com points to 104.26.12.156, 104.26.13.156 and 172.67.69.165.
Host names that point to 104.26.12.156: ns1.trafficclub.com and ns2.trafficclub.com.
Host names that point to 104.26.13.156: ns1.trafficclub.com and ns2.trafficclub.com.
Host names that point to 172.67.69.165: ns1.trafficclub.com and ns2.trafficclub.com.