microsoftdeployment.com - dns.ninja

`microsoftdeployment.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-09.azure-dns.com` ⭐
		A	2603:1061:0:700::9^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-09.azure-dns.com`
		A	13.107.236.9^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-09.azure-dns.com`
NS	`ns2-09.azure-dns.net`
		A	2620:1ec:8ec:700::9^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-09.azure-dns.net`
		A	150.171.21.9^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-09.azure-dns.net`
NS	`ns3-09.azure-dns.org`
		A	2a01:111:4000:700::9^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-09.azure-dns.org`
		A	204.14.183.9^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-09.azure-dns.org`
NS	`ns4-09.azure-dns.info`
		A	2620:1ec:bda:700::9^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-09.azure-dns.info`
		A	208.84.5.9^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-09.azure-dns.info`
SOA	`ns1-09.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=1783147461

Same first word

microsoftdeployment.com

microsoftdeployment.net

DNS History

17 records (9 active, 8 former)

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

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

○NSns1.msft.net2015-06-06 → 2017-02-18 · 4 obs

● 2015-06-06 08:14:42
● 2017-02-18 00:28:28
○ 2026-02-28 11:53:12
○ 2026-07-04 07:00:20

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

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

○NSns2.msft.net2015-06-06 → 2017-02-18 · 4 obs

● 2015-06-06 08:14:42
● 2017-02-18 00:28:28
○ 2026-02-28 11:53:12
○ 2026-07-04 07:00:20

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

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

○NSns3.msft.net2015-06-06 → 2017-02-18 · 4 obs

● 2015-06-06 08:14:42
● 2017-02-18 00:28:28
○ 2026-02-28 11:53:12
○ 2026-07-04 07:00:20

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

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

○NSns4.msft.net2015-06-06 → 2017-02-18 · 4 obs

● 2015-06-06 08:14:42
● 2017-02-18 00:28:28
○ 2026-02-28 11:53:12
○ 2026-07-04 07:00:20

●A20.112.250.1332026-02-28 → 2026-07-04 · 3 obs

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

●A20.231.239.2462026-02-28 → 2026-07-04 · 3 obs

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

●A20.236.44.1622026-02-28 → 2026-07-04 · 3 obs

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

●A20.70.246.202026-02-28 → 2026-07-04 · 3 obs

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

●A20.76.201.1712026-02-28 → 2026-07-04 · 3 obs

○ 2017-02-18 00:28:28
● 2026-02-28 11:53:12
● 2026-07-04 07:00:20

○A40.84.199.2332017-02-18 → 2017-02-18 · 4 obs

○ 2016-06-20 17:45:02
● 2017-02-18 00:28:28
○ 2026-02-28 11:53:12
○ 2026-07-04 07:00:20

○A52.178.167.1092017-02-18 → 2017-02-18 · 4 obs

○ 2016-06-20 17:45:02
● 2017-02-18 00:28:28
○ 2026-02-28 11:53:12
○ 2026-07-04 07:00:20

○A64.4.6.1002015-06-06 → 2016-06-20 · 4 obs

● 2015-06-06 08:14:42
● 2016-06-20 17:45:02
○ 2017-02-18 00:28:28
○ 2026-07-04 07:00:20

○A65.55.39.102015-06-06 → 2016-06-20 · 4 obs

● 2015-06-06 08:14:42
● 2016-06-20 17:45:02
○ 2017-02-18 00:28:28
○ 2026-07-04 07:00:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net...	-
microsoftdeployment.com	ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftdeployment.com (unsigned zone)

⏱️ Timing

Total: 454ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

microsoftdeployment.com resolves to five IP numbers: 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others

Two other host names, along with ms-visualstudiosforapplications.org, ie7.sk and extremepowerpointmakeover.com, also share IP numbers with microsoftdeployment.com.

Name Servers

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

microsoftdeployment.com has at least partial name server overlap with other domains, such as headandshoulders.fr, telekinesys.com, gucu.net and two others.

ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org all point to exactly two IP numbers each: ns1-09.azure-dns.com → 13.107.236.9 and 2603:1061:0:700::9; ns4-09.azure-dns.info → 208.84.5.9 and 2620:1ec:bda:700::9; ns2-09.azure-dns.net → 150.171.21.9 and 2620:1ec:8ec:700::9; ns3-09.azure-dns.org → 204.14.183.9 and 2a01:111:4000:700::9.