`microsoftpatch.net`

DNSSEC	⚠️ Not signed
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
TXT	`v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.aga...`
SOA	`ns1-01.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=1771291465

Same first word

microsoftpatch.net

DNS History

6 records (4 active, 2 former)

●NSns1-01.azure-dns.com2026-02-26 → 2026-02-26 · 1 obs

● 2026-02-26 12:43:36

●NSns2-01.azure-dns.net2026-02-26 → 2026-02-26 · 1 obs

● 2026-02-26 12:43:36

●NSns3-01.azure-dns.org2026-02-26 → 2026-02-26 · 1 obs

● 2026-02-26 12:43:36

●NSns4-01.azure-dns.info2026-02-26 → 2026-02-26 · 1 obs

● 2026-02-26 12:43:36

○A64.4.6.2332015-06-09 → 2016-11-28 · 3 obs

● 2015-06-09 12:38:38
● 2016-11-28 21:44:34
○ 2026-02-26 12:43:36

○A65.55.39.122015-06-09 → 2016-11-28 · 3 obs

● 2015-06-09 12:38:38
● 2016-11-28 21:44:34
○ 2026-02-26 12:43:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	b.gtld-servers.net, m.gtld-servers.net, k.gtld-servers.net, e.gtld-servers.net...	-
microsoftpatch.net	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server: 204.14.183.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftpatch.net (unsigned zone)

⏱️ Timing

Total: 1048ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
TXT	1	`v=DMARC1; p=reject; pct=100; rua=mailto:`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

AI analysis

microsoftpatch.net delegates to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

microsoftpatch.net at least partially shares name servers with other domains, for instance 154.57.in-addr.arpa, operation.us, swindonstar.com, iqit.ro and nordisketax.se.

Host names with two IP numbers: ns1-01.azure-dns.com points to 2603:1061:0:700::1 and 13.107.236.1; ns4-01.azure-dns.info points to 2620:1ec:bda:700::1 and 208.84.5.1; ns2-01.azure-dns.net points to 2620:1ec:8ec:700::1 and 150.171.21.1; ns3-01.azure-dns.org points to 2a01:111:4000:700::1 and 204.14.183.1.

microsoftpatch.net - robtex.com