`zmdomp.top`

DNSSEC	⚠️ Not signed
A	115.159.226.153^{🇨🇳 TENCENT-NET-AP115.159.226.0/23 Proxy-registered route object}
NS	`similar.dnspod.net` ⭐
		A	2402:4e00:1470:2::e^{🇨🇳 TENCENT-NET-AP2402:4e00:1400::/40}
		A	1.12.0.4^{🇨🇳 TENCENT-NET-AP-CN1.12.0.0/20 ZL-IDC-BOM}
		A	1.14.119.35^{🇨🇳 TENCENT-NET-AP1.14.64.0/18}
		A	111.13.13.35^{🇨🇳 CHINAMOBILE-CN111.13.0.0/16 CMI (Customer Route)}
		A	117.89.178.173^{🇨🇳 ChinaNet-NANJING-JISHAN-IDC117.89.176.0/21 JS-CT NJ-JS-IDC}
		A	220.196.136.35^{🇨🇳 UNICOM-SHFT-IDC220.196.136.0/24}
NS	`liqueur.dnspod.net`
		A	2402:4e00:111:fff::c^{🇨🇳 TENCENT-NET-AP2402:4e00::/35}
		A	1.12.0.1^{🇨🇳 TENCENT-NET-AP-CN1.12.0.0/20 ZL-IDC-BOM}
		A	36.155.149.176^{🇨🇳 CMNET-Jiangsu-AP36.155.144.0/21 CMI (Customer Route)}
		A	101.227.168.35^{🇨🇳 SHANGHAITELECOM101.227.168.0/23 SHIDC}
		A	111.206.98.235^{🇨🇳 CHINA169-BJ111.206.98.0/24}
		A	129.211.176.239^{🇨🇳 TENCENT-NET-AP129.211.176.0/20}
SOA	`similar.dnspod.net`freednsadmin@dnspod.com serial=1775405610

`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-05-13_07:50:01`
	SOA	`a.zdnscloud.com`td_dns_gtld@knet.cn serial=1395796465

Same first word

zmdomp.top

DNS History

4 records (3 active, 1 former)

●NSliqueur.dnspod.net2026-04-03 → 2026-05-13 · 2 obs

● 2026-04-03 13:02:18
● 2026-05-13 00:16:38

●NSsimilar.dnspod.net2026-04-03 → 2026-05-13 · 2 obs

● 2026-04-03 13:02:18
● 2026-05-13 00:16:38

●A115.159.226.1532026-04-20 → 2026-05-13 · 3 obs

○ 2026-04-03 13:02:18
● 2026-04-20 09:30:50
● 2026-05-13 00:16:38

○A124.223.162.1772026-04-03 → 2026-04-03 · 3 obs

● 2026-04-03 13:02:18
○ 2026-04-20 09:30:50
○ 2026-05-13 00:16:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
top	d.zdnscloud.com, b.zdnscloud.cn, j.zdnscloud.com, f.zdnscloud.cn...	9 records
zmdomp.top	liqueur.dnspod.net, similar.dnspod.net	-

✅ Authoritative Response

Server:117.89.178.173

NS records: liqueur.dnspod.net, similar.dnspod.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for zmdomp.top (unsigned zone)

⏱️ Timing

Total: 2536ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`115.159.226.153`
NS	2	`liqueur.dnspod.net, similar.dnspod.net`
SOA	1	`similar.dnspod.net freednsadmin.dnspod.c`

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (f.zdnscloud.cn, e.zdnscloud.cn, d.zdnscloud.com...)

Analysis

IP Addresses

zmdomp.top points to a single IP number: 115.159.226.153.

Other host names, for instance friapp.com, share IP numbers with zmdomp.top.

Name Servers

zmdomp.top is delegated to two name servers: liqueur.dnspod.net and similar.dnspod.net.

zmdomp.top uses the same name server setup as other domains, for instance trend-games.com, yeliao.net, cystudio.tech, dqpump.net and szzjx.net.

zmdomp.top shares name servers with other domains at least partially, for instance xn--xpqw1jqwd2z4a.com and ditie.com.

these name servers are often used together with the name servers f1g1ns1.dnspod.net.

Host names with six IP numbers: liqueur.dnspod.net points to 2402:4e00:111:fff::c, 1.12.0.1, 36.155.149.176, 101.227.168.35, 111.206.98.235 and 129.211.176.239; similar.dnspod.net points to 2402:4e00:1470:2::e, 1.12.0.4, 1.14.119.35, 111.13.13.35, 117.89.178.173 and 220.196.136.35.

zmdomp.top - robtex.com

zmdomp.top

top