secure-microsoft.com - dns.ninja

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

Same first word

secure-microsoft.org

secure-microsoft.net

secure-microsoft.biz

secure-microsoft.com

secure-microsoft.us

secure-microsoft.info

Similar names

microsoft-secure.net

microsoft-secure.ovh

microsoft-secure.org

DNS History

17 records (9 active, 8 former)

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

○NSns1.msft.net2015-06-05 → 2017-11-20 · 4 obs

● 2015-06-05 15:04:44
● 2017-11-20 19:35:54
○ 2026-02-28 16:30:10
○ 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

○NSns2.msft.net2015-06-05 → 2017-11-20 · 4 obs

● 2015-06-05 15:04:44
● 2017-11-20 19:35:54
○ 2026-02-28 16:30:10
○ 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

○NSns3.msft.net2015-06-05 → 2017-11-20 · 4 obs

● 2015-06-05 15:04:44
● 2017-11-20 19:35:54
○ 2026-02-28 16:30:10
○ 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

○NSns4.msft.net2015-06-05 → 2017-11-20 · 4 obs

● 2015-06-05 15:04:44
● 2017-11-20 19:35:54
○ 2026-02-28 16:30:10
○ 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

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

○ 2017-11-20 19:35:54
● 2026-02-28 16:30:10
● 2026-08-03 14:19:24

○A40.84.199.2332016-12-26 → 2017-11-20 · 5 obs

○ 2016-04-19 16:54:48
● 2016-12-26 20:45:48
● 2017-11-20 19:35:54
○ 2026-02-28 16:30:10
○ 2026-08-03 14:19:24

○A52.178.167.1092016-12-26 → 2017-11-20 · 5 obs

○ 2016-04-19 16:54:48
● 2016-12-26 20:45:48
● 2017-11-20 19:35:54
○ 2026-02-28 16:30:10
○ 2026-08-03 14:19:24

○A64.4.6.1002015-06-05 → 2016-04-19 · 4 obs

● 2015-06-05 15:04:44
● 2016-04-19 16:54:48
○ 2016-12-26 20:45:48
○ 2026-08-03 14:19:24

○A65.55.39.102015-06-05 → 2016-04-19 · 4 obs

● 2015-06-05 15:04:44
● 2016-04-19 16:54:48
○ 2016-12-26 20:45:48
○ 2026-08-03 14:19:24

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:150.171.21.7

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 444ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

secure-microsoft.com has five IP addresses, specifically 20.70.246.20, 20.76.201.171, 20.112.250.133 and two more

Among the host names that share IP numbers with secure-microsoft.com are hotmail.co.ag, xbox180accessories.info, ashesofmombasa.org and two others.

Name Servers

The domain secure-microsoft.com is delegated to these four name servers: ns1-07.azure-dns.com, ns4-07.azure-dns.info, ns2-07.azure-dns.net and ns3-07.azure-dns.org.

At least some of secure-microsoft.com's name servers are shared with other domains, for example microsoftworld.net, aui.edu, tst-cfexpress.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns1-07.azure-dns.com directs to 13.107.236.7 and 2603:1061:0:700::7; ns4-07.azure-dns.info directs to 208.84.5.7 and 2620:1ec:bda:700::7; ns2-07.azure-dns.net directs to 150.171.21.7 and 2620:1ec:8ec:700::7; ns3-07.azure-dns.org directs to 204.14.183.7 and 2a01:111:4000:700::7.