chainly.com - dns.ninja

chainly.com

com

Same first word

Similar names

DNS History

25 records (8 active, 17 former)

20162017201820192020202120222023202420252026NSns57.domaincontrol.comns58.domaincontrol.combuy.internettraffic.comdns1.registrar-servers.comdns2.registrar-servers.comdns3.registrar-servers.comdns4.registrar-servers.comdns5.registrar-servers.comns1.uniregistrymarket.linkns2.uniregistrymarket.linksell.internettraffic.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA216.150.1.1162.255.119.251192.64.119.1769.172.201.153
NSbuy.internettraffic.com2016-04-23 → 2016-04-23 · 4 obs
○ 2016-01-06 15:51:14
● 2016-04-23 10:04:24
○ 2017-01-08 20:27:26
○ 2026-08-11 06:56:34
NSdns1.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
NSdns2.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
NSdns3.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
NSdns4.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
NSdns5.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
NSns1.uniregistrymarket.link2017-01-08 → 2017-01-08 · 4 obs
○ 2016-04-23 10:04:24
● 2017-01-08 20:27:26
○ 2026-02-15 15:01:14
○ 2026-08-11 06:56:34
NSns2.uniregistrymarket.link2017-01-08 → 2017-01-08 · 4 obs
○ 2016-04-23 10:04:24
● 2017-01-08 20:27:26
○ 2026-02-15 15:01:14
○ 2026-08-11 06:56:34
NSns57.domaincontrol.com2026-02-15 → 2026-08-11 · 3 obs
○ 2017-01-08 20:27:26
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
NSns58.domaincontrol.com2026-02-15 → 2026-08-11 · 3 obs
○ 2017-01-08 20:27:26
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
NSsell.internettraffic.com2016-04-23 → 2016-04-23 · 4 obs
○ 2016-01-06 15:51:14
● 2016-04-23 10:04:24
○ 2017-01-08 20:27:26
○ 2026-08-11 06:56:34
MXalt1.aspmx.l.google.com2026-02-15 → 2026-08-11 · 3 obs
○ 2016-04-23 10:04:24
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
MXalt2.aspmx.l.google.com2026-02-15 → 2026-08-11 · 3 obs
○ 2016-04-23 10:04:24
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
MXalt3.aspmx.l.google.com2026-02-15 → 2026-08-11 · 3 obs
○ 2016-04-23 10:04:24
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
MXalt4.aspmx.l.google.com2026-02-15 → 2026-08-11 · 3 obs
○ 2016-04-23 10:04:24
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
MXaspmx.l.google.com2026-02-15 → 2026-08-11 · 3 obs
○ 2016-04-23 10:04:24
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
MXeforward1.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
MXeforward2.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
MXeforward3.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
MXeforward4.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
MXeforward5.registrar-servers.com2015-07-13 → 2016-01-06 · 4 obs
● 2015-07-13 04:38:54
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
A162.255.119.2512016-01-06 → 2016-01-06 · 4 obs
○ 2015-11-16 05:25:38
● 2016-01-06 15:51:14
○ 2016-04-23 10:04:24
○ 2026-08-11 06:56:34
A192.64.119.172015-07-13 → 2015-11-16 · 4 obs
● 2015-07-13 04:38:54
● 2015-11-16 05:25:38
○ 2016-01-06 15:51:14
○ 2026-08-11 06:56:34
A216.150.1.12026-02-15 → 2026-08-11 · 3 obs
○ 2017-01-08 20:27:26
● 2026-02-15 15:01:14
● 2026-08-11 06:56:34
A69.172.201.1532016-04-23 → 2017-01-08 · 5 obs
○ 2016-01-06 15:51:14
● 2016-04-23 10:04:24
● 2017-01-08 20:27:26
○ 2026-02-15 15:01:14
○ 2026-08-11 06:56:34

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comm.gtld-servers.net, j.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net...-
chainly.comns57.domaincontrol.com, ns58.domaincontrol.com4 records

✅ Authoritative Response

Server:173.201.76.29

NS records: ns57.domaincontrol.com, ns58.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for chainly.com (unsigned zone)

⏱️ Timing

Total: 846ms | Queries: -

📄 Records

TypeCountSample Data
A1216.150.1.1
NS2ns57.domaincontrol.com, ns58.domaincontrol.com
MX5aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...
TXT1v=spf1 include:dc-aa8e722993._spfm.chain
SOA1ns57.domaincontrol.com dns.jomax.net

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns57.domaincontrol.com, ns57.domaincontrol.com, ns58.domaincontrol.com...)

Analysis

IP Addresses

chainly.com has exactly one IP address — 216.150.1.1.

cngoogol.com, neurochain.ai, ellaskin.com plus two other host names have IP numbers in common with chainly.com.

Name Servers

The NS records for chainly.com delegate to ns57.domaincontrol.com and ns58.domaincontrol.com.

The name server configuration of chainly.com is shared with other domains, for instance thefbc.com, navshi.com, furnituresol.com and two others.

chainly.com shares at least some of its name servers with other domains, such as zafar.com.my and residentialliving.com.

ns57.domaincontrol.com resolves to 97.74.108.29 and 2603:5:21c2::1d. Likewise, ns58.domaincontrol.com resolves to 173.201.76.29 and 2603:5:22c2::1d — two IP addresses apiece.

Mail Servers

Mail for chainly.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by chainly.com are shared with other domains: amsivereach.com, ns500671.ns500731.ns500742.ns500704.ns500688.ns500688.ns500678.ns500704.ns500688.ns500291.ns500666.ns500291.ns500131.lustychickser.com, ns500742.ns500671.ns500742.ns500731.ns500704.ns500671.ns500678.ns500688.ns500704.ns500678.ns500291.tenderladiesbz.com and two others among them.

It is common to find these mail servers paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and aspmx2.googlemail.com, as well as two others.

Host names pointing to two IP addresses:

The A records for aspmx.l.google.com return 142.251.16.26 and 2607:f8b0:4004:c23::1b.

The A records for alt1.aspmx.l.google.com return 192.178.234.27 and 2800:3f0:4003:c14::1a.

The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1a.

The A records for alt3.aspmx.l.google.com return 192.178.223.27 and 2a00:1450:4009:c0f::1a.

The A records for alt4.aspmx.l.google.com return 172.253.157.26 and 2a00:1450:400c:c23::1b.