android.ren - dns.ninja
android.ren
| 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@android.ren 2025-12-20 #2 | ||||||
ren
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.zdnscloud.com ⭐ | ||||||
| NS | a.zdnscloud.cn | ||||||
| NS | b.zdnscloud.cn | ||||||
| NS | c.zdnscloud.com | ||||||
| NS | d.zdnscloud.com | ||||||
| NS | f.zdnscloud.cn | ||||||
| NS | g.zdnscloud.com | ||||||
| NS | i.zdnscloud.cn | ||||||
| NS | j.zdnscloud.com | ||||||
| TXT | 2018-04-16_11:41:46 | ||||||
| SOA | a.zdnscloud.comtd_dns_gtld@knet.cn serial=1423181818 | ||||||
Same first word
Similar names
DNS History
11 records (3 active, 8 former)
●NSns1.atom.com2026-02-25 → 2026-06-25 · 3 obs
● 2026-02-25 18:57:18
● 2026-06-25 11:44:30
○NSns1.myhostadmin.net2017-09-27 → 2017-09-27 · 3 obs
○ 2026-02-25 18:57:18
○ 2026-06-25 11:44:30
●NSns2.atom.com2026-02-25 → 2026-06-25 · 3 obs
● 2026-02-25 18:57:18
● 2026-06-25 11:44:30
○NSns2.myhostadmin.net2017-09-27 → 2017-09-27 · 3 obs
○ 2026-02-25 18:57:18
○ 2026-06-25 11:44:30
○NSns3.myhostadmin.net2017-09-27 → 2017-09-27 · 3 obs
○ 2026-02-25 18:57:18
○ 2026-06-25 11:44:30
○NSns4.myhostadmin.net2017-09-27 → 2017-09-27 · 3 obs
○ 2026-02-25 18:57:18
○ 2026-06-25 11:44:30
○NSns5.myhostadmin.net2017-09-27 → 2017-09-27 · 3 obs
○ 2026-02-25 18:57:18
○ 2026-06-25 11:44:30
○NSns6.myhostadmin.net2017-09-27 → 2017-09-27 · 3 obs
○ 2026-02-25 18:57:18
○ 2026-06-25 11:44:30
○A118.193.11.342017-09-27 → 2017-09-27 · 4 obs
● 2017-09-27 11:28:24
○ 2026-02-25 18:57:18
○ 2026-06-25 11:44:30
○A23.27.192.1152016-12-09 → 2016-12-09 · 3 obs
○ 2017-09-27 11:28:24
○ 2026-06-25 11:44:30
●A52.20.84.622026-02-25 → 2026-06-25 · 3 obs
● 2026-02-25 18:57:18
● 2026-06-25 11:44:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ren | a.zdnscloud.cn, c.zdnscloud.com, i.zdnscloud.cn, g.zdnscloud.com... | 8 records |
| android.ren | ns1.atom.com, ns2.atom.com | - |
✅ Authoritative Response
Server:50.19.240.86
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for android.ren (unsigned zone)
⏱️ Timing
Total: 1012ms | 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.android.ren |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (g.zdnscloud.com, f.zdnscloud.cn, d.zdnscloud.com...)
Analysis
IP Addresses
android.ren resolves to one IP address: 52.20.84.62.
openmdx.com, www.clicktracker.io, finestall.com and two other host names share IP numbers with android.ren.
Name Servers
DNS delegation for android.ren points to two name servers: ns1.atom.com and ns2.atom.com.
android.ren uses the same name servers as several other domains — among them kanoba.com, mwlf.com, portalradio.com and two more.
The name servers for android.ren are partially shared with other domains like inksac.com, apeo.org and fusionbug.com
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.