runpi.com - dns.ninja
runpi.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=1751342668 | ||||||
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=1785661097 | ||||||
Same first word
runpi.com |
Similar names
DNS History
10 records (2 active, 8 former)
○NSdns1.iidns.com2015-08-27 → 2016-12-11 · 4 obs
● 2016-12-11 21:44:04
○ 2026-02-19 09:30:42
○ 2026-08-02 09:28:14
○NSdns2.iidns.com2015-08-27 → 2016-12-11 · 4 obs
● 2016-12-11 21:44:04
○ 2026-02-19 09:30:42
○ 2026-08-02 09:28:14
○NSdns3.iidns.com2015-08-27 → 2016-12-11 · 4 obs
● 2016-12-11 21:44:04
○ 2026-02-19 09:30:42
○ 2026-08-02 09:28:14
○NSdns4.iidns.com2015-08-27 → 2016-12-11 · 4 obs
● 2016-12-11 21:44:04
○ 2026-02-19 09:30:42
○ 2026-08-02 09:28:14
○NSdns5.iidns.com2015-08-27 → 2016-12-11 · 4 obs
● 2016-12-11 21:44:04
○ 2026-02-19 09:30:42
○ 2026-08-02 09:28:14
○NSdns6.iidns.com2015-08-27 → 2017-01-14 · 4 obs
● 2017-01-14 14:13:14
○ 2026-02-19 09:30:42
○ 2026-08-02 09:28:14
●NSns1.ename.net2026-02-19 → 2026-08-02 · 3 obs
● 2026-02-19 09:30:42
● 2026-08-02 09:28:14
●NSns2.ename.net2026-02-19 → 2026-08-02 · 3 obs
● 2026-02-19 09:30:42
● 2026-08-02 09:28:14
○A101.78.223.1312015-08-27 → 2016-12-11 · 4 obs
● 2016-12-11 21:44:04
○ 2026-02-19 09:30:42
○ 2026-08-02 09:28:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net... | - |
| runpi.com | ns1.ename.net, ns2.ename.net | - |
✅ Authoritative Response
Server:218.98.111.173
NS records: ns1.ename.net, ns2.ename.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for runpi.com (unsigned zone)
⏱️ Timing
Total: 1151ms | 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
runpi.com is served by two delegated name servers, ns1.ename.net and ns2.ename.net.
runpi.com has the same name server delegation as a number of other domains, such as qaha.com, champselysees.cn, 4250.com and two more.
At least some of runpi.com's name servers are shared with other domains, for example huasin.com, qepc.com, baiduid.cn and two more.
These name servers tend to co-occur with ns3.dns.com, ns4.dns.com, ns3.ename.net and 3 other name servers in the same DNS delegations.
Hosts pointing to four IP addresses:
ns2.ename.net directs 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:
ns1.ename.net resolves to three addresses: 61.158.128.31, 218.98.111.173 and 2001:df2:f080:1::8.