`io05ry.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`
	NS	`f.zdnscloud.cn`
	NS	`i.zdnscloud.cn`
	NS	`j.zdnscloud.com`
	TXT	`2026-07-16_02:35:01`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1396468377

⚠️ On DNS blocklist: tif

Subdomains

330bs210.io05ry.top

Same first word

io05ry.top

DNS History

6 records (6 active, 0 former)

●NSns1.myhostadmin.net2026-04-04 → 2026-07-15 · 2 obs

● 2026-04-04 19:01:36
● 2026-07-15 19:26:52

●NSns2.myhostadmin.net2026-04-04 → 2026-07-15 · 2 obs

● 2026-04-04 19:01:36
● 2026-07-15 19:26:52

●NSns3.myhostadmin.net2026-04-04 → 2026-07-15 · 2 obs

● 2026-04-04 19:01:36
● 2026-07-15 19:26:52

●NSns4.myhostadmin.net2026-04-04 → 2026-07-15 · 2 obs

● 2026-04-04 19:01:36
● 2026-07-15 19:26:52

●NSns5.myhostadmin.net2026-04-04 → 2026-07-15 · 2 obs

● 2026-04-04 19:01:36
● 2026-07-15 19:26:52

●NSns6.myhostadmin.net2026-04-04 → 2026-07-15 · 2 obs

● 2026-04-04 19:01:36
● 2026-07-15 19:26:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
top	a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com, d.zdnscloud.com...	-
io05ry.top	ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net...	-

✅ Authoritative Response

Server:61.172.183.73

NS records: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for io05ry.top (unsigned zone)

⏱️ Timing

Total: 563ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	6	`ns3.myhostadmin.net, ns5.myhostadmin.net...`
SOA	1	`ns1.myhostadmin.net dnsconct.myhostadmin`

Analysis

Hierarchy

io05ry.top is the parent zone for 330bs210.io05ry.top.

Name Servers

io05ry.top is delegated to 6 name servers: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net and 3 other.

io05ry.top partially shares its NS delegation with several other domains, including gzw.net, 12rc.com, baslife.cn and two others.

In DNS configurations, these name servers often share authority with ns5.myhostadmin.net, ns4.myhostadmin.net, ns6.myhostadmin.net and 6 other name servers.

Host names resolving to four IP addresses:

ns1.myhostadmin.net maps to the following IP addresses: 60.247.150.254, 118.123.249.114, 118.123.253.132 and 240e:d9:c200::2.

ns2.myhostadmin.net maps to the following IP addresses: 61.172.183.73, 61.240.129.143, 211.149.230.100 and 240e:d9:c200:1::2.

Host names with three IP numbers:

ns3.myhostadmin.net points to 61.172.183.77, 118.123.249.114 and 240e:d9:c200::2.

ns4.myhostadmin.net points to 118.123.253.132, 211.149.230.100 and 240e:d9:c200:1::2.

ns5.myhostadmin.net points to 61.172.183.73, 118.123.249.114 and 240e:d9:c200::2.

ns6.myhostadmin.net points to 60.247.150.13, 118.123.253.132 and 240e:d9:c200:1::2.

ns1.myhostadmin.net, ns3.myhostadmin.net and ns5.myhostadmin.net are host names that all point to 240e:d9:c200::2.

ns1.myhostadmin.net, ns3.myhostadmin.net and ns5.myhostadmin.net are host names that all point to 118.123.249.114.

ns1.myhostadmin.net, ns4.myhostadmin.net and ns6.myhostadmin.net are host names that all point to 118.123.253.132.

ns2.myhostadmin.net, ns4.myhostadmin.net and ns6.myhostadmin.net are host names that all point to 240e:d9:c200:1::2.