loopower.com - robtex.com
loopower.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 | ||||||
| PTR | 31.128.158.61.ha.cnc | ||||||
| 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 Proxy-registered route object | ||||||
| SOA | ns1.ename.netadmin@ename.net serial=1751342761 | ||||||
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=1778802721 | ||||||
Previously MX for
loopower.com |
Same first word
loopower.com |
DNS History
16 records (2 active, 14 former)
○NSns1.busywebs.com2008-03-19 → 2008-03-19 · 3 obs
● 2008-03-19 12:31:12
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
●NSns1.ename.net2026-03-18 → 2026-05-15 · 3 obs
○ 2017-12-23 09:41:36
● 2026-03-18 03:11:18
● 2026-05-15 00:07:36
● 2026-03-18 03:11:18
● 2026-05-15 00:07:36
○NSns1cnb.domain-resolution.net2015-05-31 → 2016-12-01 · 5 obs
○ 2008-03-19 12:31:12
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
○NSns1cnb.name.com2017-12-23 → 2017-12-23 · 4 obs
○ 2016-12-01 18:03:40
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
○NSns2.busywebs.com2008-03-19 → 2008-03-19 · 3 obs
● 2008-03-19 12:31:12
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
●NSns2.ename.net2026-03-18 → 2026-05-15 · 3 obs
○ 2017-12-23 09:41:36
● 2026-03-18 03:11:18
● 2026-05-15 00:07:36
● 2026-03-18 03:11:18
● 2026-05-15 00:07:36
○NSns2hkt.domain-resolution.net2015-05-31 → 2016-12-01 · 5 obs
○ 2008-03-19 12:31:12
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
○NSns2hkt.name.com2017-12-23 → 2017-12-23 · 4 obs
○ 2016-12-01 18:03:40
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
○NSns3cna.domain-resolution.net2015-05-31 → 2016-12-01 · 5 obs
○ 2008-03-19 12:31:12
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
○NSns3cna.name.com2017-12-23 → 2017-12-23 · 4 obs
○ 2016-12-01 18:03:40
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
○NSns4kpx.domain-resolution.net2015-05-31 → 2016-12-01 · 5 obs
○ 2008-03-19 12:31:12
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
● 2015-05-31 06:14:48
● 2016-12-01 18:03:40
○ 2017-12-23 09:41:36
○ 2026-05-15 00:07:36
○NSns4kpx.name.com2017-12-23 → 2017-12-23 · 4 obs
○ 2016-12-01 18:03:40
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
○MXloopower.com2008-03-19 → 2008-03-19 · 3 obs
● 2008-03-19 12:31:12
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
○A104.236.129.222016-01-26 → 2017-12-23 · 5 obs
○ 2015-10-26 12:43:52
● 2016-01-26 11:54:20
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
● 2016-01-26 11:54:20
● 2017-12-23 09:41:36
○ 2026-03-18 03:11:18
○ 2026-05-15 00:07:36
○A174.37.49.1312015-05-31 → 2015-10-26 · 5 obs
○ 2008-03-19 12:31:12
● 2015-05-31 06:14:48
● 2015-10-26 12:43:52
○ 2016-01-26 11:54:20
○ 2026-05-15 00:07:36
● 2015-05-31 06:14:48
● 2015-10-26 12:43:52
○ 2016-01-26 11:54:20
○ 2026-05-15 00:07:36
○A58.145.192.762008-03-19 → 2008-03-19 · 3 obs
● 2008-03-19 12:31:12
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
○ 2015-05-31 06:14:48
○ 2026-05-15 00:07:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net... | - |
| loopower.com | ns1.ename.net, ns2.ename.net | - |
✅ Authoritative Response
Server:61.158.128.31
NS records: ns1.ename.net, ns2.ename.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for loopower.com (unsigned zone)
⏱️ Timing
Total: 692ms | 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 ns1.ename.net and ns2.ename.net are delegated to loopower.com.
loopower.com uses the same name server configuration as other domains, such as ptfdcw.com, qdnrb.com, malazhubo.com, chaoshen.com.cn and 77pi.com.
loopower.com shares name servers with other domains at least partially, for instance quzhuan.net, u1q.com, 0594.cn and nuz.com.
These name servers are commonly used with ns3.dns.com and ns4.dns.com.
Four IP numbers for host names:
ns2.ename.net points to: 240e:97d:10:1402:0:1:0:1005, 1.193.216.198, 183.253.57.199 and 211.99.99.52.
Three IP numbers for host names:
ns1.ename.net points to: 2001:df2:f080:1::8, 61.158.128.31 and 218.98.111.173.