`cryptotelegraph.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	`2e43e638-ca3e-49c7-8a97-15641558bcb6`
SOA	`ns1.atom.com`hostmaster@cryptotelegraph.com 2026-03-04 #67

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

Same first word

cryptotelegraph.com

DNS History

6 records (3 active, 3 former)

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

○ 2017-08-12 23:38:58
● 2026-03-15 23:47:16
● 2026-03-16 15:38:52

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

○ 2017-08-12 23:38:58
● 2026-03-15 23:47:16
● 2026-03-16 15:38:52

○NSns53.domaincontrol.com2017-08-12 → 2017-08-12 · 3 obs

● 2017-08-12 23:38:58
○ 2026-03-15 23:47:16
○ 2026-03-16 15:38:52

○NSns54.domaincontrol.com2017-08-12 → 2017-08-12 · 3 obs

● 2017-08-12 23:38:58
○ 2026-03-15 23:47:16
○ 2026-03-16 15:38:52

○A50.63.202.452017-08-12 → 2017-08-12 · 3 obs

● 2017-08-12 23:38:58
○ 2026-03-15 23:47:16
○ 2026-03-16 15:38:52

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

○ 2017-08-12 23:38:58
● 2026-03-15 23:47:16
● 2026-03-16 15:38:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
cryptotelegraph.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 cryptotelegraph.com (unsigned zone)

⏱️ Timing

Total: 3268ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.20.84.62`
NS	2	`ns1.atom.com, ns2.atom.com`
TXT	1	`2e43e638-ca3e-49c7-8a97-15641558bcb6`
SOA	1	`ns1.atom.com hostmaster.cryptotelegraph.`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

cryptotelegraph.com points to a single IP number: 52.20.84.62.

other host names for instance microfinancecompany.com, whoabox.com, klembo.com, drinksglasses.com and hipstervalley.com share IP numbers with cryptotelegraph.com.

Name Servers

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

cryptotelegraph.com shares the same name server setup as other domains, for example mapvalley.com, interactivecloud.com, alpscore.com, rainloop.com and nutrixy.com.

cryptotelegraph.com partially shares name servers with other domains, for instance gaags.com, biobem.com and aibills.com.

These name servers are commonly used with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.

Host names with one IP number:

The host ns1.atom.com points to 44.219.81.145 and the host ns2.atom.com points to 50.19.240.86.

cryptotelegraph.com - robtex.com