`h3z.us`

CNAME	`302.paike-dns.cc`
DNSSEC	⚠️ Not signed
A	64.186.224.78^{🇺🇸 GTT-BACKBONE64.186.224.0/19 GTT}
		PTR	`302.paike.us`
A	154.17.27.13^{🇺🇸 DMIT-AS906154.17.27.0/24 DMIT}

`us`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.cctld.us` ⭐
	NS	`b.cctld.us`
	NS	`f.cctld.us`
	NS	`k.cctld.us`
	NS	`m.cctld.us`
	NS	`n.cctld.us`
	NS	`w.cctld.us`
	NS	`x.cctld.us`
	NS	`y.cctld.us`
	SOA	`a.cctld.us`admin@tldns.godaddy serial=1775937019

Same first word

h3z.de

h3z.jp

h3z.com

h3z.net

h3z.org

h3z.cn

h3z.us

h3z.ph

Similar names

3hz.ru

3hz.ch

3hz.org

hz3.ru

zh3.net

3hz.com

3hz.jp

3hz.co.jp

z3h.net

3hz.info

3hz.de

3zh.ru

3zh.fr

hz3.net

z3h.com

zh3.ch

3zh.net

hz3.com

3zh.de

hz3.de

hz3.ir

3hz.net

zh3.cn

DNS History

4 records (3 active, 1 former)

●NSns1.dyna-ns.net2026-02-16 → 2026-04-11 · 2 obs

● 2026-02-16 13:25:12
● 2026-04-11 20:04:00

●NSns2.dyna-ns.net2026-02-16 → 2026-04-11 · 2 obs

● 2026-02-16 13:25:12
● 2026-04-11 20:04:00

●CNAME302.paike-dns.cc2026-03-29 → 2026-04-11 · 3 obs

○ 2026-02-17 01:32:14
● 2026-03-29 20:23:00
● 2026-04-11 20:04:00

○CNAME302.paike567.top2026-02-16 → 2026-02-17 · 4 obs

● 2026-02-16 13:25:12
● 2026-02-17 01:32:14
○ 2026-03-29 20:23:00
○ 2026-04-11 20:04:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
us	m.cctld.us, x.cctld.us, b.cctld.us, n.cctld.us...	-
h3z.us	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.27.158

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for h3z.us (unsigned zone)

⏱️ Timing

Total: 812ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns2.dyna-ns.net, ns1.dyna-ns.net`
CNAME	1	`302.paike-dns.cc`
SOA	1	`ns1.dyna-ns.net hostmaster.h3z.us`

Analysis

IP Addresses

h3z.us resolves to two IP numbers: 64.186.224.78 and 154.17.27.13.

Other host names share IP numbers with h3z.us; for instance 302.paike-dns.cc.

h3z.us - robtex.com

h3z.us

us