`annihilationevent.com`

DNSSEC	⚠️ Not signed
A	54.166.73.139^{🇺🇸 Amazon54.166.0.0/15 EC2 IAD prefix}
		PTR	`ec2-54-166-73-139.compute-1.amazonaws.com`
A	54.204.236.30^{🇺🇸 Amazon54.204.0.0/15 EC2 IAD Prefix}
NS	`ns1.cargo.site` ⭐
		A	44.205.91.121^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ns1.cargo.site`
NS	`ns2.cargo.site`
		A	100.21.27.241^{🇺🇸 Amazon100.20.0.0/14 EC2 PDX prefix}
			PTR	`ns2.cargo.site`
SOA	`ns1.cargo.site`hostmaster@annihilationevent.com 2025-07-29 #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=1784241842

Same first word

annihilationevent.com

DNS History

10 records (4 active, 6 former)

○NSdns1.name-services.com2017-01-03 → 2017-12-01 · 4 obs

● 2017-01-03 08:23:18
● 2017-12-01 15:23:40
○ 2026-04-04 18:24:44
○ 2026-07-16 23:10:36

○NSdns2.name-services.com2017-01-03 → 2017-12-01 · 4 obs

● 2017-01-03 08:23:18
● 2017-12-01 15:23:40
○ 2026-04-04 18:24:44
○ 2026-07-16 23:10:36

○NSdns3.name-services.com2017-01-03 → 2017-12-01 · 4 obs

● 2017-01-03 08:23:18
● 2017-12-01 15:23:40
○ 2026-04-04 18:24:44
○ 2026-07-16 23:10:36

○NSdns4.name-services.com2017-01-03 → 2017-12-01 · 4 obs

● 2017-01-03 08:23:18
● 2017-12-01 15:23:40
○ 2026-04-04 18:24:44
○ 2026-07-16 23:10:36

○NSdns5.name-services.com2017-01-03 → 2017-12-01 · 4 obs

● 2017-01-03 08:23:18
● 2017-12-01 15:23:40
○ 2026-04-04 18:24:44
○ 2026-07-16 23:10:36

●NSns1.cargo.site2026-04-04 → 2026-07-16 · 3 obs

○ 2017-12-01 15:23:40
● 2026-04-04 18:24:44
● 2026-07-16 23:10:36

●NSns2.cargo.site2026-04-04 → 2026-07-16 · 3 obs

○ 2017-12-01 15:23:40
● 2026-04-04 18:24:44
● 2026-07-16 23:10:36

●A54.166.73.1392026-04-04 → 2026-07-16 · 3 obs

○ 2017-12-01 15:23:40
● 2026-04-04 18:24:44
● 2026-07-16 23:10:36

●A54.204.236.302026-04-04 → 2026-07-16 · 3 obs

○ 2017-12-01 15:23:40
● 2026-04-04 18:24:44
● 2026-07-16 23:10:36

○A72.3.239.592017-01-03 → 2017-12-01 · 4 obs

● 2017-01-03 08:23:18
● 2017-12-01 15:23:40
○ 2026-04-04 18:24:44
○ 2026-07-16 23:10:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
annihilationevent.com	ns1.cargo.site, ns2.cargo.site	-

✅ Authoritative Response

Server:44.205.91.121

NS records: ns1.cargo.site, ns2.cargo.site

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for annihilationevent.com (unsigned zone)

⏱️ Timing

Total: 245ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`54.166.73.139, 54.204.236.30`
NS	2	`ns1.cargo.site, ns2.cargo.site`
SOA	1	`ns1.cargo.site hostmaster.annihilationev`

Analysis

IP Addresses

annihilationevent.com points to the IP addresses 54.166.73.139 and 54.204.236.30

Among the host names that share IP numbers with annihilationevent.com are olivergoulding.com, anjafonseka.ch, googleimages.org and two others.

Name Servers

DNS delegation for annihilationevent.com points to two name servers: ns1.cargo.site and ns2.cargo.site.

annihilationevent.com has the same name server delegation as a number of other domains, such as dayclub.studio, yuanfang.me, mikestupin.com and two more.

The name servers of annihilationevent.com overlap at least partially with those of other domains — among them gwbell.com, panita.co, kevinhuang.info and two more.

The name servers ns1.cargocollective.com, ns2.cargocollective.com and a.misconfigured.dns.server.invalid are commonly seen alongside these name servers.

Both ns1.cargo.site and ns2.cargo.site have a single IP address each — ns1.cargo.site resolves to 44.205.91.121 while ns2.cargo.site resolves to 100.21.27.241.

annihilationevent.com - robtex.com