`microsoftcriticalupdates.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-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	`ip-13-107-236-4.defastlink.net`
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	`ip-150-171-21-4.defastlink.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	`ip-204-14-183-4.defastlink.net`
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	`ip-208-84-5-4.defastlink.net`
SOA	`ns1-04.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

microsoftcriticalupdates.com

DNS History

17 records (9 active, 8 former)

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

○NSns1.msft.net2015-05-24 → 2017-04-04 · 4 obs

● 2015-05-24 05:31:56
● 2017-04-04 07:48:58
○ 2026-02-28 11:07:48
○ 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

○NSns2.msft.net2015-05-24 → 2017-04-04 · 4 obs

● 2015-05-24 05:31:56
● 2017-04-04 07:48:58
○ 2026-02-28 11:07:48
○ 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

○NSns3.msft.net2015-05-24 → 2017-04-04 · 4 obs

● 2015-05-24 05:31:56
● 2017-04-04 07:48:58
○ 2026-02-28 11:07:48
○ 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

○NSns4.msft.net2015-05-24 → 2017-04-04 · 4 obs

● 2015-05-24 05:31:56
● 2017-04-04 07:48:58
○ 2026-02-28 11:07:48
○ 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

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

○ 2017-04-04 07:48:58
● 2026-02-28 11:07:48
● 2026-03-24 04:10:42

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

○ 2016-08-12 13:56:30
● 2017-04-04 07:48:58
○ 2026-02-28 11:07:48
○ 2026-03-24 04:10:42

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

○ 2016-08-12 13:56:30
● 2017-04-04 07:48:58
○ 2026-02-28 11:07:48
○ 2026-03-24 04:10:42

○A64.4.6.1002015-05-24 → 2016-08-12 · 4 obs

● 2015-05-24 05:31:56
● 2016-08-12 13:56:30
○ 2017-04-04 07:48:58
○ 2026-03-24 04:10:42

○A65.55.39.102015-05-24 → 2016-08-12 · 4 obs

● 2015-05-24 05:31:56
● 2016-08-12 13:56:30
○ 2017-04-04 07:48:58
○ 2026-03-24 04:10:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
microsoftcriticalupdates.com	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:150.171.21.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 microsoftcriticalupdates.com (unsigned zone)

⏱️ Timing

Total: 914ms | 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 (ns1-04.azure-dns.com, ns1-04.azure-dns.com)

Analysis

IP Addresses

Five IP numbers are pointed to by microsoftcriticalupdates.com: 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 skypeconnect.net, gethotmail.org, kingofbingmaps.com, bingprogramming.com and sharepoinsite.com share IP numbers with microsoftcriticalupdates.com.

Name Servers

microsoftcriticalupdates.com's delegation is handled by four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

microsoftcriticalupdates.com partially shares name servers with other domains; examples include hidraqua.info, goclickexpress.com, microsoftlive.net, tadm.sg and publicloud.com.br.

Host names with two IPs:

ns1-04.azure-dns.com points to 2603:1061:0:700::4 and 13.107.236.4

ns4-04.azure-dns.info points to 2620:1ec:bda:700::4 and 208.84.5.4

ns2-04.azure-dns.net points to 2620:1ec:8ec:700::4 and 150.171.21.4

ns3-04.azure-dns.org points to 2a01:111:4000:700::4 and 204.14.183.4

microsoftcriticalupdates.com - robtex.com