microsoftpatch.info - dns.ninja

`microsoftpatch.info`

DNSSEC	⚠️ Not signed
A	20.70.246.20^{🇦🇺 Microsoft20.64.0.0/10}
A	20.76.201.171^{🇳🇱 Microsoft20.64.0.0/10}
A	20.112.250.133^{🇺🇸 Microsoft20.64.0.0/10}
A	20.231.239.246^{🇺🇸 Microsoft20.192.0.0/10}
A	20.236.44.162^{🇺🇸 Microsoft20.192.0.0/10}
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`
SOA	`ns1-04.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`info`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.info.afilias-nst.info` ⭐
	NS	`a2.info.afilias-nst.info`
	NS	`b0.info.afilias-nst.org` ⚠️ Not in parent delegation
	NS	`b2.info.afilias-nst.org` ⚠️ Not in parent delegation
	NS	`c0.info.afilias-nst.info`
	NS	`d0.info.afilias-nst.org` ⚠️ Not in parent delegation
	SOA	`a0.info.afilias-nst.info`hostmaster@donuts.email serial=1780987259

Same first word

microsoftpatch.us

microsoftpatch.info

microsoftpatch.org

microsoftpatch.net

microsoftpatch.biz

microsoftpatch.com

DNS History

17 records (9 active, 8 former)

●NSns1-04.azure-dns.com2026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

○NSns1.msft.net2015-07-12 → 2017-04-10 · 4 obs

● 2015-07-12 07:44:38
● 2017-04-10 07:55:10
○ 2026-02-28 16:10:04
○ 2026-06-09 07:26:18

●NSns2-04.azure-dns.net2026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

○NSns2.msft.net2015-07-12 → 2017-04-10 · 4 obs

● 2015-07-12 07:44:38
● 2017-04-10 07:55:10
○ 2026-02-28 16:10:04
○ 2026-06-09 07:26:18

●NSns3-04.azure-dns.org2026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

○NSns3.msft.net2015-07-12 → 2017-04-10 · 4 obs

● 2015-07-12 07:44:38
● 2017-04-10 07:55:10
○ 2026-02-28 16:10:04
○ 2026-06-09 07:26:18

●NSns4-04.azure-dns.info2026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

○NSns4.msft.net2015-07-12 → 2017-04-10 · 4 obs

● 2015-07-12 07:44:38
● 2017-04-10 07:55:10
○ 2026-02-28 16:10:04
○ 2026-06-09 07:26:18

●A20.112.250.1332026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

●A20.231.239.2462026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

●A20.236.44.1622026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

●A20.70.246.202026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

●A20.76.201.1712026-02-28 → 2026-06-09 · 3 obs

○ 2017-04-10 07:55:10
● 2026-02-28 16:10:04
● 2026-06-09 07:26:18

○A40.84.199.2332017-01-09 → 2017-04-10 · 5 obs

○ 2016-04-29 15:04:04
● 2017-01-09 21:42:38
● 2017-04-10 07:55:10
○ 2026-02-28 16:10:04
○ 2026-06-09 07:26:18

○A52.178.167.1092017-01-09 → 2017-04-10 · 5 obs

○ 2016-04-29 15:04:04
● 2017-01-09 21:42:38
● 2017-04-10 07:55:10
○ 2026-02-28 16:10:04
○ 2026-06-09 07:26:18

○A64.4.6.1002015-07-12 → 2016-04-29 · 4 obs

● 2015-07-12 07:44:38
● 2016-04-29 15:04:04
○ 2017-01-09 21:42:38
○ 2026-06-09 07:26:18

○A65.55.39.102015-07-12 → 2016-04-29 · 4 obs

● 2015-07-12 07:44:38
● 2016-04-29 15:04:04
○ 2017-01-09 21:42:38
○ 2026-06-09 07:26:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
info	a0.info.afilias-nst.info, a2.info.afilias-nst.info, c0.info.afilias-nst.info	-
microsoftpatch.info	ns1-04.azure-dns.com, ns3-04.azure-dns.org, ns2-04.azure-dns.net, ns4-04.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.21.4

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftpatch.info (unsigned zone)

⏱️ Timing

Total: 524ms | Queries: -

📄 Records

Type	Count	Sample Data
A	5	`20.76.201.171, 20.112.250.133...`
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
SOA	1	`ns1-04.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns4-04.azure-dns.info, ns4-04.azure-dns.info)

Analysis

IP Addresses

microsoftpatch.info points to 5 IP numbers: 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others.

Additional host names — genee.co, groove.mobi, xbox.co and two others — share IP numbers with microsoftpatch.info.

Name Servers

Authority for microsoftpatch.info is delegated across 4 name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

microsoftpatch.info has at least partial name server overlap with other domains, such as pharmalex.com, mido.ca, robochamps.org 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.