`seeminglyrandom.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	`ip-44-219-81-145.defastlink.net`
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.com`hostmaster@seeminglyrandom.com 2025-10-08 #3

`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=1776312597

Previously MX for

seeminglyrandom.com

Same first word

seeminglyrandom.com

DNS History

7 records (3 active, 4 former)

●NSns1.atom.com2026-03-26 → 2026-04-16 · 3 obs

○ 2017-10-01 06:16:18
● 2026-03-26 15:21:56
● 2026-04-16 04:32:52

○NSns1.speedydns.net2015-08-15 → 2017-10-01 · 4 obs

● 2015-08-15 18:38:06
● 2017-10-01 06:16:18
○ 2026-03-26 15:21:56
○ 2026-04-16 04:32:52

●NSns2.atom.com2026-03-26 → 2026-04-16 · 3 obs

○ 2017-10-01 06:16:18
● 2026-03-26 15:21:56
● 2026-04-16 04:32:52

○NSns2.speedydns.net2015-08-15 → 2017-10-01 · 4 obs

● 2015-08-15 18:38:06
● 2017-10-01 06:16:18
○ 2026-03-26 15:21:56
○ 2026-04-16 04:32:52

○MXseeminglyrandom.com2015-08-15 → 2017-10-01 · 4 obs

● 2015-08-15 18:38:06
● 2017-10-01 06:16:18
○ 2026-03-26 15:21:56
○ 2026-04-16 04:32:52

○A149.47.132.1572015-08-15 → 2017-10-01 · 4 obs

● 2015-08-15 18:38:06
● 2017-10-01 06:16:18
○ 2026-03-26 15:21:56
○ 2026-04-16 04:32:52

●A52.20.84.622026-03-26 → 2026-04-16 · 3 obs

○ 2017-10-01 06:16:18
● 2026-03-26 15:21:56
● 2026-04-16 04:32:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, m.gtld-servers.net, j.gtld-servers.net, g.gtld-servers.net...	-
seeminglyrandom.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 seeminglyrandom.com (unsigned zone)

⏱️ Timing

Total: 3128ms | 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.seeminglyrandom.`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

seeminglyrandom.com points to a single IP address: 52.20.84.62.

Other host names such as www.vertvision.com, sandovalconstruction.com, warpstore.com, www.combatskin.com and deltongo.com share IP numbers with seeminglyrandom.com.

Name Servers

seeminglyrandom.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.

seeminglyrandom.com uses the same name server setup as other domains, including amplocity.com, saviorshield.com, homeground.net, thunderfist.com and futuresfunding.com.

At least part of the name servers for seeminglyrandom.com are shared with other domains, for instance medvora.com, untalked.com, bipq.com, livoe.com and dotgods.com.

Hostnames with a single IP

ns1.atom.com resolves to: 44.219.81.145.

ns2.atom.com resolves to: 50.19.240.86.

seeminglyrandom.com - robtex.com