`iduhuk.top`

DNSSEC	⚠️ Not signed
NS	`ns1.myhostadmin.net` ⭐
		A	240e:d9:c200::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	60.247.150.254^{🇨🇳 CHINANET-SCIDC-AS-AP60.247.128.0/18 SICHUANIDC province network}
		A	118.123.249.114^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
		A	118.123.253.132^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
NS	`ns2.myhostadmin.net`
		A	240e:d9:c200:1::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	61.172.183.73^{🇨🇳 SHANGHAITELECOM61.172.182.0/23 SHIDC}
		A	61.240.129.143^{🇨🇳 CHINA169-Backbone61.240.128.0/19 CMI (Customer Route)}
		A	211.149.230.100^{🇨🇳 CHINANET-SCIDC-AS-AP211.149.224.0/19 chinanet SC province network-client}
NS	`ns3.myhostadmin.net`
		A	240e:d9:c200::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	61.172.183.77^{🇨🇳 SHANGHAITELECOM61.172.182.0/23 SHIDC}
		A	118.123.249.114^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
NS	`ns4.myhostadmin.net`
		A	240e:d9:c200:1::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	118.123.253.132^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
		A	211.149.230.100^{🇨🇳 CHINANET-SCIDC-AS-AP211.149.224.0/19 chinanet SC province network-client}
NS	`ns5.myhostadmin.net`
		A	240e:d9:c200::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	61.172.183.73^{🇨🇳 SHANGHAITELECOM61.172.182.0/23 SHIDC}
		A	118.123.249.114^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
NS	`ns6.myhostadmin.net`
		A	240e:d9:c200:1::2^{🇨🇳 CHINANET-SCIDC-AS-AP240e:d9:c000::/36 SICHUANIDC province network}
		A	60.247.150.13^{🇨🇳 CHINANET-SCIDC-AS-AP60.247.128.0/18 SICHUANIDC province network}
		A	118.123.253.132^{🇨🇳 CHINANET-SCIDC-AS-AP118.123.240.0/20 CHINANET SiChuan Telecom Internet Data Center}
SOA	`ns1.myhostadmin.net`dnsconct@myhostadmin.net 2025-08-17 #4

`top`

	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	`e.zdnscloud.cn` ⚠️ Not in parent delegation
	NS	`f.zdnscloud.cn`
	NS	`g.zdnscloud.com` ⚠️ Not in zone NS records
	NS	`i.zdnscloud.cn`
	NS	`j.zdnscloud.com`
	TXT	`2026-04-14_16:35:01`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1395536518

⚠️ On DNS blocklist: tif

Subdomains

330bs074.iduhuk.top

Same first word

iduhuk.top

DNS History

6 records (6 active, 0 former)

●NSns1.myhostadmin.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 09:37:06
● 2026-04-14 08:44:46

●NSns2.myhostadmin.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 09:37:06
● 2026-04-14 08:44:46

●NSns3.myhostadmin.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 09:37:06
● 2026-04-14 08:44:46

●NSns4.myhostadmin.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 09:37:06
● 2026-04-14 08:44:46

●NSns5.myhostadmin.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 09:37:06
● 2026-04-14 08:44:46

●NSns6.myhostadmin.net2026-04-02 → 2026-04-14 · 2 obs

● 2026-04-02 09:37:06
● 2026-04-14 08:44:46

🔍 DNS Trace

Analysis

Hierarchy

The parent of 330bs074.iduhuk.top is iduhuk.top.

Name Servers

iduhuk.top delegates to six name servers: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net and ns6.myhostadmin.net.

iduhuk.top shares name servers with other domains at least partially, for instance pzfcyy.cn, additel.com.cn, lfweh.com, nc123.net and handouer.cn.