referencemonitor.com - dns.ninja
referencemonitor.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 ⭐ | ||||||
| NS | ns2.atom.com | ||||||
| TXT | c356c182-fb79-4ea9-934d-c892384e0081 | ||||||
| TXT | afternic-verification-4AQ5pU3CHThBNzvs3r7jmM | ||||||
| TXT | 4b39cde4b0c178350793fa5fe4e6b79d7c3a1ed6 | ||||||
| SOA | ns1.atom.comhostmaster@referencemonitor.com 2026-08-24 #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.netnstld@verisign-grs.com serial=1790079809 | ||||||
Same first word
referencemonitor.com |
Similar names
DNS History
18 records (3 active, 15 former)
○NSns0.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
●NSns1.atom.com2026-08-29 → 2026-09-22 · 3 obs
○ 2018-12-30 05:18:08
● 2026-08-29 15:23:30
● 2026-09-22 12:41:38
● 2026-08-29 15:23:30
● 2026-09-22 12:41:38
○NSns1.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○NSns1.sedoparking.com2018-12-30 → 2018-12-30 · 4 obs
○ 2017-02-04 22:13:50
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
●NSns2.atom.com2026-08-29 → 2026-09-22 · 3 obs
○ 2018-12-30 05:18:08
● 2026-08-29 15:23:30
● 2026-09-22 12:41:38
● 2026-08-29 15:23:30
● 2026-09-22 12:41:38
○NSns2.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○NSns2.sedoparking.com2018-12-30 → 2018-12-30 · 4 obs
○ 2017-02-04 22:13:50
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
○NSns3.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○MXlocalhost2018-12-30 → 2018-12-30 · 4 obs
○ 2017-02-04 22:13:50
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
○MXmx0.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○MXmx1.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○MXmx2.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○MXmx3.dnssec.net2015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
●A52.20.84.622026-08-29 → 2026-09-22 · 3 obs
○ 2018-12-30 05:18:08
● 2026-08-29 15:23:30
● 2026-09-22 12:41:38
● 2026-08-29 15:23:30
● 2026-09-22 12:41:38
○A72.52.4.1192018-12-30 → 2018-12-30 · 4 obs
○ 2017-02-04 22:13:50
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
○A80.69.68.212015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○A80.69.78.2472015-07-11 → 2017-02-04 · 4 obs
● 2015-07-11 09:46:18
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
● 2017-02-04 22:13:50
○ 2018-12-30 05:18:08
○ 2026-09-22 12:41:38
○A91.195.240.2402018-12-30 → 2018-12-30 · 4 obs
○ 2017-02-04 22:13:50
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
● 2018-12-30 05:18:08
○ 2026-08-29 15:23:30
○ 2026-09-22 12:41:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, b.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net... | - |
| referencemonitor.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 referencemonitor.com (unsigned zone)
⏱️ Timing
Total: 4594ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| TXT | 3 | c356c182-fb79-4ea9-934d-c892384e0081, afternic-verification-4AQ5pU3CHThBNzvs3r... |
| SOA | 1 | ns1.atom.com hostmaster.referencemonitor |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
referencemonitor.com directs to one IP number, which is 52.20.84.62.
Name Servers
referencemonitor.com has two authoritative name servers — ns1.atom.com and ns2.atom.com.