sangku.com - robtex.com
sangku.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 | ||||||
| SOA | ns1.ename.netadmin@ename.net serial=1751342770 | ||||||
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=1786463329 | ||||||
Same first word
sangku.com |
Similar names
DNS History
17 records (2 active, 15 former)
○NSdns1.iidns.com2015-07-19 → 2017-03-24 · 5 obs
○ 2008-03-09 14:39:58
● 2015-07-19 02:26:36
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
● 2015-07-19 02:26:36
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○NSdns15.hichina.com2008-03-09 → 2008-03-09 · 3 obs
● 2008-03-09 14:39:58
○ 2015-07-19 02:26:36
○ 2026-08-11 16:07:38
○ 2015-07-19 02:26:36
○ 2026-08-11 16:07:38
○NSdns16.hichina.com2008-03-09 → 2008-03-09 · 3 obs
● 2008-03-09 14:39:58
○ 2015-07-19 02:26:36
○ 2026-08-11 16:07:38
○ 2015-07-19 02:26:36
○ 2026-08-11 16:07:38
○NSdns2.iidns.com2015-07-19 → 2015-07-19 · 4 obs
○ 2008-03-09 14:39:58
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
○NSdns3.iidns.com2015-07-19 → 2015-07-19 · 4 obs
○ 2008-03-09 14:39:58
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
○NSdns4.iidns.com2015-07-19 → 2015-07-19 · 4 obs
○ 2008-03-09 14:39:58
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
○NSdns5.iidns.com2015-07-19 → 2015-07-19 · 4 obs
○ 2008-03-09 14:39:58
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
● 2015-07-19 02:26:36
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
○NSdns6.iidns.com2015-07-19 → 2016-03-06 · 5 obs
○ 2008-03-09 14:39:58
● 2015-07-19 02:26:36
● 2016-03-06 15:26:56
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
● 2015-07-19 02:26:36
● 2016-03-06 15:26:56
○ 2017-03-24 04:55:22
○ 2026-08-11 16:07:38
●NSns1.ename.net2026-04-09 → 2026-08-11 · 3 obs
○ 2017-03-24 04:55:22
● 2026-04-09 12:27:30
● 2026-08-11 16:07:38
● 2026-04-09 12:27:30
● 2026-08-11 16:07:38
●NSns2.ename.net2026-04-09 → 2026-08-11 · 3 obs
○ 2017-03-24 04:55:22
● 2026-04-09 12:27:30
● 2026-08-11 16:07:38
● 2026-04-09 12:27:30
● 2026-08-11 16:07:38
○A103.241.230.1352017-03-24 → 2017-03-24 · 4 obs
○ 2015-07-19 02:26:36
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○A103.241.230.1372017-03-24 → 2017-03-24 · 4 obs
○ 2015-07-19 02:26:36
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○A103.241.230.1382017-03-24 → 2017-03-24 · 4 obs
○ 2015-07-19 02:26:36
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○A103.241.230.1392017-03-24 → 2017-03-24 · 4 obs
○ 2015-07-19 02:26:36
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
● 2017-03-24 04:55:22
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○A198.148.92.872015-07-19 → 2015-07-19 · 3 obs
● 2015-07-19 02:26:36
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○A198.148.92.882015-07-19 → 2015-07-19 · 3 obs
● 2015-07-19 02:26:36
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
○ 2026-04-09 12:27:30
○ 2026-08-11 16:07:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| sangku.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 sangku.com (unsigned zone)
⏱️ Timing
Total: 1064ms | 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 sangku.com: ns1.ename.net and ns2.ename.net.
sangku.com shares its NS records with other domains, for example qze.com.cn, maxiaoteng.com, fgrf.cn and two others.
Host names that resolve to four IP numbers:
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.
Hostnames that map to three IP numbers:
The hostname ns1.ename.net points to 61.158.128.31, 218.98.111.173 and 2001:df2:f080:1::8.