attackaction.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`attackaction.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`
TXT	`f0095018235b8109a2bf9f65674a1784b6971ed6`
SOA	`ns1.atom.com`hostmaster@attackaction.com 2025-10-14 #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.net`nstld@verisign-grs.com serial=1787018214

Same first word

attackaction.com

Previous names

Next names

DNS History

7 records (3 active, 4 former)

●NSns1.atom.com2026-02-16 → 2026-08-18 · 3 obs

○ 2019-03-23 18:40:48
● 2026-02-16 05:33:38
● 2026-08-18 02:10:42

○NSns1.brandbucket.com2019-03-23 → 2019-03-23 · 3 obs

● 2019-03-23 18:40:48
○ 2026-02-16 05:33:38
○ 2026-08-18 02:10:42

●NSns2.atom.com2026-02-16 → 2026-08-18 · 3 obs

○ 2019-03-23 18:40:48
● 2026-02-16 05:33:38
● 2026-08-18 02:10:42

○NSns2.brandbucket.com2019-03-23 → 2019-03-23 · 3 obs

● 2019-03-23 18:40:48
○ 2026-02-16 05:33:38
○ 2026-08-18 02:10:42

○A2600:1f1c:800:8b00:f57b:5e93:f0f1:8b2f2019-03-23 → 2019-03-23 · 3 obs

● 2019-03-23 18:40:48
○ 2026-02-16 05:33:38
○ 2026-08-18 02:10:42

●A52.20.84.622026-02-16 → 2026-08-18 · 3 obs

○ 2019-03-23 18:40:48
● 2026-02-16 05:33:38
● 2026-08-18 02:10:42

○A54.183.99.632019-03-23 → 2019-03-23 · 3 obs

● 2019-03-23 18:40:48
○ 2026-02-16 05:33:38
○ 2026-08-18 02:10:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, l.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net...	-
attackaction.com	ns1.atom.com, ns2.atom.com	2 records

✅ Authoritative Response

Server:50.19.240.86

NS records: ns1.atom.com, ns2.atom.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for attackaction.com (unsigned zone)

⏱️ Timing

Total: 155ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.20.84.62`
NS	2	`ns2.atom.com, ns1.atom.com`
TXT	1	`f0095018235b8109a2bf9f65674a1784b6971ed6`
SOA	1	`ns1.atom.com hostmaster.attackaction.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)

Analysis

IP Addresses

attackaction.com resolves to one IP address: 52.20.84.62.

cryptobabe.com, altdevs.com, web7.online and two other host names share IP numbers with attackaction.com.

Name Servers

Two name servers handle the delegation for attackaction.com: ns1.atom.com and ns2.atom.com.

attackaction.com uses the same name servers as several other domains — among them oxcite.com, merge.me, dasiko.com and two more.

The name servers for attackaction.com are at least partly shared with other domains such as triolago.com, ploybase.com, pleasurine.com and pubways.com.

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.