`hydrapi.net`

DNSSEC	⚠️ Not signed
A	40.68.16.89^{🇳🇱 Microsoft40.68.0.0/14}
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
NS	`ns3-04.azure-dns.org`
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-04.azure-dns.org`
NS	`ns4-04.azure-dns.info`
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
MX	`aspmx.l.google.com` ⭐
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4025:402::1a^{🇳🇱 Google2a00:1450:4025::/48}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.26^{🇺🇸 Google142.250.102.0/24}
			PTR	`rb-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f26.1e100.net`
		A	192.178.213.27^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4001:c21::1a^{🇩🇪 Google2a00:1450:4001::/48}
			PTR	`lcfrai-in-f26.1e100.net`
		A	142.251.127.27^{🇺🇸 Google142.251.127.0/24}
			PTR	`lcfrai-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4025:4401::1b^{🇮🇪 Google2a00:1450:4025::/48}
			PTR	`yuskedq-in-f27.1e100.net`
		A	172.253.148.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yuskedq-in-f26.1e100.net`
TXT	`google-site-verification=VOS88OG5kGc4Q6KfvtznRgK2ee4WBxjruIro8qyG98o`
SOA	`ns1-04.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`net`

	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=1784098472

📈 Tranco rank: #152,791

Subdomains

stun.hydrapi.net

Same first word

hydrapi.net

Similar names

riyadhp.com

hipyard.net

DNS History

10 records (10 active, 0 former)

●NSns1-04.azure-dns.com2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●NSns2-04.azure-dns.net2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●NSns3-04.azure-dns.org2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●NSns4-04.azure-dns.info2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●MXalt1.aspmx.l.google.com2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●MXalt2.aspmx.l.google.com2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●MXalt3.aspmx.l.google.com2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●MXalt4.aspmx.l.google.com2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●MXaspmx.l.google.com2026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

●A40.68.16.892026-03-06 → 2026-07-15 · 2 obs

● 2026-03-06 17:58:12
● 2026-07-15 07:17:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	f.gtld-servers.net, g.gtld-servers.net, i.gtld-servers.net, c.gtld-servers.net...	-
hydrapi.net	ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.4

NS records: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hydrapi.net (unsigned zone)

⏱️ Timing

Total: 547ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`40.68.16.89`
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`google-site-verification=VOS88OG5kGc4Q6K`
SOA	1	`ns1-04.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-04.azure-dns.net, ns2-04.azure-dns.net)

Analysis

Hierarchy

hydrapi.net serves as the parent of stun.hydrapi.net.

IP Addresses

hydrapi.net resolves to just one IP address, 40.68.16.89.

Other host names, such as wwzapi.com, share IP numbers with hydrapi.net.

Name Servers

The NS records for hydrapi.net point to four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

hydrapi.net has at least partial name server overlap with other domains, such as c1.centralus.azure.app.snowflake.com, azurestack.network, mintral.cl and two others.

ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org all point to exactly two IP numbers each: ns1-04.azure-dns.com → 13.107.236.4 and 2603:1061:0:700::4; ns4-04.azure-dns.info → 208.84.5.4 and 2620:1ec:bda:700::4; ns2-04.azure-dns.net → 150.171.21.4 and 2620:1ec:8ec:700::4; ns3-04.azure-dns.org → 204.14.183.4 and 2a01:111:4000:700::4.