`mongodbmonitoring.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.com`hostmaster@mongodbmonitoring.com 2025-02-21 #5

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

Same first word

mongodbmonitoring.com

DNS History

9 records (3 active, 6 former)

○NSa.dns.gandi.net2015-05-29 → 2020-03-13 · 4 obs

● 2015-05-29 07:21:20
● 2020-03-13 14:57:44
○ 2026-07-03 08:38:40
○ 2026-07-17 14:57:30

○NSb.dns.gandi.net2015-05-29 → 2020-03-13 · 4 obs

● 2015-05-29 07:21:20
● 2020-03-13 14:57:44
○ 2026-07-03 08:38:40
○ 2026-07-17 14:57:30

○NSc.dns.gandi.net2015-05-29 → 2020-03-13 · 4 obs

● 2015-05-29 07:21:20
● 2020-03-13 14:57:44
○ 2026-07-03 08:38:40
○ 2026-07-17 14:57:30

●NSns1.atom.com2026-07-03 → 2026-07-17 · 3 obs

○ 2020-03-13 14:57:44
● 2026-07-03 08:38:40
● 2026-07-17 14:57:30

●NSns2.atom.com2026-07-03 → 2026-07-17 · 3 obs

○ 2020-03-13 14:57:44
● 2026-07-03 08:38:40
● 2026-07-17 14:57:30

○MXfb.mail.gandi.net2015-05-29 → 2020-03-13 · 4 obs

● 2015-05-29 07:21:20
● 2020-03-13 14:57:44
○ 2026-07-03 08:38:40
○ 2026-07-17 14:57:30

○MXspool.mail.gandi.net2015-05-29 → 2020-03-13 · 4 obs

● 2015-05-29 07:21:20
● 2020-03-13 14:57:44
○ 2026-07-03 08:38:40
○ 2026-07-17 14:57:30

○A217.70.184.382015-05-29 → 2020-03-13 · 4 obs

● 2015-05-29 07:21:20
● 2020-03-13 14:57:44
○ 2026-07-03 08:38:40
○ 2026-07-17 14:57:30

●A52.20.84.622026-07-03 → 2026-07-17 · 3 obs

○ 2020-03-13 14:57:44
● 2026-07-03 08:38:40
● 2026-07-17 14:57:30

🔍 DNS Trace

📋 Delegation Chain

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

⏱️ Timing

Total: 3543ms | 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.mongodbmonitorin`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

mongodbmonitoring.com resolves to just one IP address, 52.20.84.62.

Two other host names, along with devil.net, futtitinni.com and orangepalace.com, also share IP numbers with mongodbmonitoring.com.

Name Servers

mongodbmonitoring.com has two authoritative name servers — ns1.atom.com and ns2.atom.com.

mongodbmonitoring.com shares its NS records with other domains, for example ruoja.com, astalo.com, cleansewell.com and two others.

The name servers of mongodbmonitoring.com overlap at least partially with those of other domains — among them soxna.com, extraultra.com, decuro.com and two more.

These name servers commonly appear in combination with the name servers verification-6b2kjcxkmj36igckssq5sn.ns101.verify.hn.

Both ns1.atom.com and ns2.atom.com have a single IP address each — ns1.atom.com resolves to 44.219.81.145 while ns2.atom.com resolves to 50.19.240.86.

mongodbmonitoring.com - robtex.com