ensensor.com - dns.ninja
ensensor.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@ensensor.com 2026-06-27 #2 | ||||||
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=1782625365 | ||||||
Same first word
ensensor.com |
Similar names
DNS History
14 records (3 active, 11 former)
○NSlaunch1.spaceship.net2026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 15:08:52
○ 2026-06-13 01:20:38
○ 2026-06-28 06:02:30
○NSlaunch2.spaceship.net2026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 15:08:52
○ 2026-06-13 01:20:38
○ 2026-06-28 06:02:30
●NSns1.atom.com2026-06-13 → 2026-06-28 · 3 obs
● 2026-06-13 01:20:38
● 2026-06-28 06:02:30
○NSns17.xincache.com2016-12-21 → 2018-06-23 · 4 obs
● 2018-06-23 20:26:20
○ 2026-02-24 14:18:08
○ 2026-06-28 06:02:30
○NSns18.xincache.com2016-12-21 → 2018-06-23 · 4 obs
● 2018-06-23 20:26:20
○ 2026-02-24 14:18:08
○ 2026-06-28 06:02:30
●NSns2.atom.com2026-06-13 → 2026-06-28 · 3 obs
● 2026-06-13 01:20:38
● 2026-06-28 06:02:30
○NSns3.afternic.com2026-02-24 → 2026-02-24 · 4 obs
● 2026-02-24 14:18:08
○ 2026-03-25 15:08:52
○ 2026-06-28 06:02:30
○NSns4.afternic.com2026-02-24 → 2026-02-24 · 4 obs
● 2026-02-24 14:18:08
○ 2026-03-25 15:08:52
○ 2026-06-28 06:02:30
○MX.2026-02-24 → 2026-06-28 · 2 obs
○ 2026-06-28 06:02:30
○A13.248.169.482026-02-24 → 2026-02-24 · 3 obs
○ 2026-03-25 15:08:52
○ 2026-06-28 06:02:30
○A44.232.173.2492026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 15:08:52
○ 2026-06-13 01:20:38
○ 2026-06-28 06:02:30
●A52.20.84.622026-06-13 → 2026-06-28 · 3 obs
● 2026-06-13 01:20:38
● 2026-06-28 06:02:30
○A52.40.42.1132026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 15:08:52
○ 2026-06-13 01:20:38
○ 2026-06-28 06:02:30
○A76.223.54.1462026-02-24 → 2026-02-24 · 3 obs
○ 2026-03-25 15:08:52
○ 2026-06-28 06:02:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ensensor.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 ensensor.com (unsigned zone)
⏱️ Timing
Total: 3201ms | 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.ensensor.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
ensensor.com points to a single IP number: 52.20.84.62.
Additional host names — deskdown.com, trickmode.com, conecton.com and two others — share IP numbers with ensensor.com.
Name Servers
ensensor.com is served by two delegated name servers, ns1.atom.com and ns2.atom.com.
ensensor.com shares its name server setup with other domains, including nutrera.com, kegpal.com, bombfun.com and two others.
Some of ensensor.com's name servers are also used by other domains, including rudom.com, lhq.in, aratube.com and korea(0x736578)y.com.
These name servers are regularly seen alongside ns3.afternic.com and ns4.afternic.com as name servers.
ns1.atom.com resolves to 44.219.81.145. ns2.atom.com resolves to 50.19.240.86. Both host names point to a single IP number.