`microsoft-patch.com`

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-02.azure-dns.com` ⭐
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns2-02.azure-dns.net`
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org`
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info`
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
SOA	`ns1-02.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`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=1771291435

Same first word

microsoft-patch.net

microsoft-patch.us

microsoft-patch.biz

microsoft-patch.info

microsoft-patch.com

microsoft-patch.org

DNS History

18 records (9 active, 9 former)

●NSns1-02.azure-dns.com2026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

○NSns1.msft.net2008-03-18 → 2017-04-04 · 4 obs

● 2008-03-18 17:23:50
● 2017-04-04 21:30:52
○ 2026-02-28 11:30:32
○ 2026-03-22 06:27:26

●NSns2-02.azure-dns.net2026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

○NSns2.msft.net2008-03-18 → 2017-04-04 · 4 obs

● 2008-03-18 17:23:50
● 2017-04-04 21:30:52
○ 2026-02-28 11:30:32
○ 2026-03-22 06:27:26

●NSns3-02.azure-dns.org2026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

○NSns3.msft.net2008-03-18 → 2017-04-04 · 4 obs

● 2008-03-18 17:23:50
● 2017-04-04 21:30:52
○ 2026-02-28 11:30:32
○ 2026-03-22 06:27:26

●NSns4-02.azure-dns.info2026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

○NSns4.msft.net2008-03-18 → 2017-04-04 · 4 obs

● 2008-03-18 17:23:50
● 2017-04-04 21:30:52
○ 2026-02-28 11:30:32
○ 2026-03-22 06:27:26

○NSns5.msft.net2008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 17:23:50
○ 2015-06-24 14:11:24
○ 2026-03-22 06:27:26

●A20.112.250.1332026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

●A20.231.239.2462026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

●A20.236.44.1622026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

●A20.70.246.202026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

●A20.76.201.1712026-02-28 → 2026-03-22 · 3 obs

○ 2017-04-04 21:30:52
● 2026-02-28 11:30:32
● 2026-03-22 06:27:26

○A40.84.199.2332017-04-04 → 2017-04-04 · 4 obs

○ 2016-08-17 19:30:44
● 2017-04-04 21:30:52
○ 2026-02-28 11:30:32
○ 2026-03-22 06:27:26

○A52.178.167.1092017-04-04 → 2017-04-04 · 4 obs

○ 2016-08-17 19:30:44
● 2017-04-04 21:30:52
○ 2026-02-28 11:30:32
○ 2026-03-22 06:27:26

○A64.4.6.1002015-06-24 → 2016-08-17 · 5 obs

○ 2008-03-18 17:23:50
● 2015-06-24 14:11:24
● 2016-08-17 19:30:44
○ 2017-04-04 21:30:52
○ 2026-03-22 06:27:26

○A65.55.39.102015-06-24 → 2016-08-17 · 5 obs

○ 2008-03-18 17:23:50
● 2015-06-24 14:11:24
● 2016-08-17 19:30:44
○ 2017-04-04 21:30:52
○ 2026-03-22 06:27:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
microsoft-patch.com	ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info	2 records

✅ Authoritative Response

Server: 150.171.21.2

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoft-patch.com (unsigned zone)

⏱️ Timing

Total: 433ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)

Analysis

IP Addresses

microsoft-patch.com points to five IP numbers: 20.70.246.20, 20.76.201.171, 20.112.250.133, 20.231.239.246 and 20.236.44.162.

Other host names, for instance halomaga.com, microsoftaudienceads.ca, ohtmail.com, skype-korea.or.kr and surfaceflick.com share IP numbers with microsoft-patch.com.

Name Servers

microsoft-patch.com is delegated to four name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

microsoft-patch.com at least partially shares its name servers with other domains, for instance ageofkings.cz, microsoft-p.net, ecovital.com.br, noutatipm.ro and prudentialcarolinas.com.

Host names with two IPs: ns1-02.azure-dns.com points to 2603:1061:0:700::2 and 13.107.236.2; ns4-02.azure-dns.info points to 2620:1ec:bda:700::2 and 208.84.5.2; ns2-02.azure-dns.net points to 2620:1ec:8ec:700::2 and 150.171.21.2; ns3-02.azure-dns.org points to 2a01:111:4000:700::2 and 204.14.183.2.

microsoft-patch.com - robtex.com