`h5secure.com`

DNSSEC	⚠️ Not signed
A	54.66.184.135^{🇦🇺 Amazon54.66.128.0/17 EC2 SYD prefix}
		PTR	`ec2-54-66-184-135.ap-southeast-2.compute.amazonaws.com`
NS	`ns1.netregistry.net` ⭐
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns2.netregistry.net`
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns3.netregistry.net`
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c06::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dz-in-f27.1e100.net`
		A	142.251.2.26^{🇺🇸 Google142.251.2.0/24}
			PTR	`dl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽²⁰⁾
		A	2607:f8b0:4023:3003::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f26.1e100.net`
		A	172.253.145.27^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽³⁰⁾
		A	2a00:1450:4025:402::1b^{🇳🇱 Google2a00:1450:4025::/48}
			PTR	`rb-in-f27.1e100.net`
		A	142.250.102.27^{🇺🇸 Google142.250.102.0/24}
			PTR	`rb-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`google-site-verification=_MpuYTqxOVv0vZRCndPSLnCe0vsaSv4qATyFiQlBacM`
SOA	`ns1.netregistry.net`dmain@netregistry.net 2023-11-13 #0

`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.net`nstld@verisign-grs.com serial=1777259556

Same first word

h5secure.com

DNS History

10 records (9 active, 1 former)

●NSns1.netregistry.net2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

●NSns2.netregistry.net2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

●NSns3.netregistry.net2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

●MXalt1.aspmx.l.google.com2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

●MXalt2.aspmx.l.google.com2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

●MXaspmx.l.google.com2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

●MXaspmx2.googlemail.com2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

●MXaspmx3.googlemail.com2015-07-26 → 2026-04-27 · 2 obs

● 2015-07-26 04:18:22
● 2026-04-27 03:27:50

○A204.93.213.452015-07-26 → 2017-02-05 · 4 obs

● 2015-07-26 04:18:22
● 2017-02-05 21:53:46
○ 2019-01-23 21:21:50
○ 2026-04-27 03:27:50

●A54.66.184.1352019-01-23 → 2026-04-27 · 3 obs

○ 2017-02-05 21:53:46
● 2019-01-23 21:21:50
● 2026-04-27 03:27:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net...	-
h5secure.com	ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net	-

✅ Authoritative Response

Server:76.223.26.245

NS records: ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for h5secure.com (unsigned zone)

⏱️ Timing

Total: 553ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.66.184.135`
NS	3	`ns2.netregistry.net, ns3.netregistry.net...`
MX	5	`ASPMX.L.GOOGLE.com (pri: 10), ASPMX3.GOOGLEMAIL.com (pri: 30)...`
TXT	1	`google-site-verification=_MpuYTqxOVv0vZR`
SOA	1	`ns1.netregistry.net dmain.netregistry.ne`