attackchains.com - dns.ninja
attackchains.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@attackchains.com 2026-09-28 #1 | ||||||
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=1794771528 | ||||||
Same first word
attackchains.com |
Similar names
Previous names
Next names
DNS History
9 records (3 active, 6 former)
●NSns1.atom.com2026-09-13 → 2026-11-15 · 3 obs
● 2026-09-13 02:56:12
● 2026-11-15 19:55:32
○NSns1.sedoparking.com2015-06-25 → 2017-11-24 · 4 obs
● 2017-11-24 17:06:58
○ 2026-09-13 02:56:12
○ 2026-11-15 19:55:32
●NSns2.atom.com2026-09-13 → 2026-11-15 · 3 obs
● 2026-09-13 02:56:12
● 2026-11-15 19:55:32
○NSns2.sedoparking.com2015-06-25 → 2017-11-24 · 4 obs
● 2017-11-24 17:06:58
○ 2026-09-13 02:56:12
○ 2026-11-15 19:55:32
○MXlocalhost2016-09-23 → 2017-11-24 · 5 obs
● 2016-09-23 17:19:00
● 2017-11-24 17:06:58
○ 2026-09-13 02:56:12
○ 2026-11-15 19:55:32
○MXmail.nickstel.com2015-06-25 → 2016-04-14 · 4 obs
● 2016-04-14 11:17:24
○ 2016-09-23 17:19:00
○ 2026-11-15 19:55:32
●A52.20.84.622026-09-13 → 2026-11-15 · 3 obs
● 2026-09-13 02:56:12
● 2026-11-15 19:55:32
○A72.52.4.1222017-11-24 → 2017-11-24 · 4 obs
● 2017-11-24 17:06:58
○ 2026-09-13 02:56:12
○ 2026-11-15 19:55:32
○A72.52.4.912015-06-25 → 2016-09-23 · 4 obs
● 2016-09-23 17:19:00
○ 2017-11-24 17:06:58
○ 2026-11-15 19:55:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| attackchains.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for attackchains.com (unsigned zone)
⏱️ Timing
Total: 3602ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.attackchains.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
attackchains.com has exactly one IP address — 52.20.84.62.
bandaluigipini.com, baardos.com, friento.com plus two other host names have IP numbers in common with attackchains.com.
Name Servers
attackchains.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
The name server configuration of attackchains.com is shared with other domains, for instance omote-nurse.com, wholebud.com, thinkway.xyz and two others.
attackchains.com has at least partial name server overlap with other domains, such as hubmembers.com, frontvault.com, agenticelevation.com and two others.
ns1.atom.com directs to 44.219.81.145 and ns2.atom.com directs to 50.19.240.86; each host name points to exactly one IP number.