eliulan.com - dns.ninja
eliulan.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.ename.net ⭐ | ||||||
| A | 2001:df2:f080:1::8🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 61.158.128.31🇨🇳 CHINA169-Backbone61.158.128.0/17 CNC Group CHINA169 Henan Province Network | ||||||
| A | 218.98.111.173🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| NS | ns2.ename.net | ||||||
| A | 240e:97d:10:1402:0:1:0:1005🇨🇳 CHINANET-Guangdong-DongGuan-IDC240e:97d::/36 DongGuan IDC Network | ||||||
| A | 1.193.216.198🇨🇳 CHINANET-Henan-Luoyang-IDC1.193.216.0/24 Chinatelecom HeNan Province Network | ||||||
| A | 183.253.57.199🇨🇳 CHINAMOBILE-CN183.253.0.0/16 CMI (Customer Route) | ||||||
| A | 211.99.99.52🇨🇳 DONGGUAN-1211.99.99.0/24 | ||||||
| SOA | ns1.ename.netadmin@ename.net serial=1751342692 | ||||||
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=1786467109 | ||||||
Same first word
eliulan.com |
Similar names
aluline.com |
aluline.be |
launiel.net |
luanlei.com |
aluline.gr |
lunaile.co.kr |
aluline.se |
aluline.com.au |
lunalie.com |
aluline.pl |
aluline.pt |
luniela.com |
unilale.com |
leanlui.com |
illenau.info |
aluline.ae |
DNS History
17 records (2 active, 15 former)
○NSdns1.iidns.com2015-06-30 → 2016-04-19 · 4 obs
● 2015-06-30 19:56:52
● 2016-04-19 16:54:06
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
● 2016-04-19 16:54:06
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○NSdns2.iidns.com2015-06-30 → 2016-04-19 · 4 obs
● 2015-06-30 19:56:52
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
○NSdns3.iidns.com2015-06-30 → 2016-04-19 · 4 obs
● 2015-06-30 19:56:52
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
○NSdns4.iidns.com2015-06-30 → 2016-04-19 · 4 obs
● 2015-06-30 19:56:52
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
○NSdns5.iidns.com2015-06-30 → 2016-04-19 · 4 obs
● 2015-06-30 19:56:52
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
○NSdns6.iidns.com2015-06-30 → 2016-04-19 · 4 obs
● 2015-06-30 19:56:52
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
● 2016-04-19 16:54:06
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
●NSns1.ename.net2026-03-22 → 2026-08-11 · 3 obs
○ 2017-11-19 18:18:34
● 2026-03-22 19:22:20
● 2026-08-11 17:18:42
● 2026-03-22 19:22:20
● 2026-08-11 17:18:42
●NSns2.ename.net2026-03-22 → 2026-08-11 · 3 obs
○ 2017-11-19 18:18:34
● 2026-03-22 19:22:20
● 2026-08-11 17:18:42
● 2026-03-22 19:22:20
● 2026-08-11 17:18:42
○NSns3.dns.com2017-11-19 → 2017-11-19 · 4 obs
○ 2016-04-19 16:54:06
● 2017-11-19 18:18:34
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
● 2017-11-19 18:18:34
○ 2026-03-22 19:22:20
○ 2026-08-11 17:18:42
○A198.148.92.482015-11-06 → 2015-11-06 · 4 obs
○ 2015-06-30 19:56:52
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○A198.148.92.492015-11-06 → 2015-11-06 · 4 obs
○ 2015-06-30 19:56:52
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○A198.148.92.532015-06-30 → 2015-11-06 · 4 obs
● 2015-06-30 19:56:52
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○A198.148.92.562015-06-30 → 2015-06-30 · 3 obs
● 2015-06-30 19:56:52
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○A198.148.92.572015-11-06 → 2015-11-06 · 4 obs
○ 2015-06-30 19:56:52
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○A198.148.92.582015-06-30 → 2015-06-30 · 3 obs
● 2015-06-30 19:56:52
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
○A198.148.92.622015-06-30 → 2015-11-06 · 4 obs
● 2015-06-30 19:56:52
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
● 2015-11-06 19:51:20
○ 2017-11-19 18:18:34
○ 2026-08-11 17:18:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net... | - |
| eliulan.com | ns1.ename.net, ns2.ename.net | - |
✅ Authoritative Response
Server:211.99.99.52
NS records: ns1.ename.net, ns2.ename.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for eliulan.com (unsigned zone)
⏱️ Timing
Total: 4098ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.ename.net, ns2.ename.net |
| SOA | 1 | ns1.ename.net admin.ename.net |
Analysis
Name Servers
Two name servers handle the delegation for eliulan.com: ns1.ename.net and ns2.ename.net.
eliulan.com has the same name server delegation as a number of other domains, such as shucard.com, zibu.net, 1cool.cn and two more.
There is an overlap in name servers between eliulan.com and other domains, for example sf75.com, 333ex.com and 62696.com
These name servers commonly appear alongside the name servers ns3.dns.com and ns4.dns.com.
Hosts pointing to four IP addresses:
ns2.ename.net resolves to 1.193.216.198, 183.253.57.199, 211.99.99.52 and 240e:97d:10:1402:0:1:0:1005.
Hosts with three IP address records:
The hostname ns1.ename.net points to 61.158.128.31, 218.98.111.173 and 2001:df2:f080:1::8.