empiredb.com - dns.ninja
empiredb.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.comhostmaster@empiredb.com 2025-11-04 #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=1785471802 | ||||||
Same first word
empiredb.com |
Similar names
DNS History
13 records (3 active, 10 former)
○NSdns10.hichina.com2015-11-20 → 2017-02-02 · 5 obs
● 2015-11-20 04:23:46
● 2017-02-02 18:29:14
○ 2026-03-27 21:11:24
○ 2026-07-31 04:44:00
○NSdns9.hichina.com2015-11-20 → 2017-02-02 · 5 obs
● 2015-11-20 04:23:46
● 2017-02-02 18:29:14
○ 2026-03-27 21:11:24
○ 2026-07-31 04:44:00
○NSlaunch1.spaceship.net2026-03-27 → 2026-07-31 · 2 obs
○ 2026-07-31 04:44:00
○NSlaunch2.spaceship.net2026-03-27 → 2026-07-31 · 2 obs
○ 2026-07-31 04:44:00
●NSns1.atom.com2026-03-27 → 2026-07-31 · 3 obs
● 2026-03-27 21:11:24
● 2026-07-31 04:44:00
●NSns2.atom.com2026-03-27 → 2026-07-31 · 3 obs
● 2026-03-27 21:11:24
● 2026-07-31 04:44:00
○NSns23.domaincontrol.com2015-07-03 → 2015-07-03 · 3 obs
○ 2015-11-20 04:23:46
○ 2026-07-31 04:44:00
○NSns24.domaincontrol.com2015-07-03 → 2015-07-03 · 3 obs
○ 2015-11-20 04:23:46
○ 2026-07-31 04:44:00
○MXmxdomain.qq.com2015-07-03 → 2017-02-02 · 4 obs
● 2017-02-02 18:29:14
○ 2026-03-27 21:11:24
○ 2026-07-31 04:44:00
○A44.232.173.2492026-03-27 → 2026-07-31 · 2 obs
○ 2026-07-31 04:44:00
○A50.63.202.362015-07-03 → 2015-07-03 · 3 obs
○ 2015-11-20 04:23:46
○ 2026-07-31 04:44:00
●A52.20.84.622026-03-27 → 2026-07-31 · 3 obs
● 2026-03-27 21:11:24
● 2026-07-31 04:44:00
○A52.40.42.1132026-03-27 → 2026-07-31 · 2 obs
○ 2026-07-31 04:44:00
🔍 DNS Trace
Analysis
IP Addresses
empiredb.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with capner.com, hotoke.com and kiaai.com, also share IP numbers with empiredb.com.
Name Servers
empiredb.com uses two name servers for its delegation: ns1.atom.com and ns2.atom.com.
empiredb.com shares its NS records with other domains, for example philes.com, dognet.net, payaba.com and two others.
There is at least partial name server overlap between empiredb.com and other domains — tatwer.com, bitcourse.com, corzap.com and two more among them.
These name servers are routinely deployed together with the name servers verification-yhehuhyrvixzqbtydgzisf.ns101.verify.hn.
ns1.atom.com → 44.219.81.145 and ns2.atom.com → 50.19.240.86: one IP number per host name.