secure-microsoft.us - dns.ninja

`secure-microsoft.us`

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

`us`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.cctld.us` ⭐
	NS	`b.cctld.us`
	NS	`f.cctld.us`
	NS	`k.cctld.us`
	NS	`m.cctld.us`
	NS	`n.cctld.us`
	NS	`w.cctld.us`
	NS	`x.cctld.us`
	NS	`y.cctld.us`
	SOA	`a.cctld.us`admin@tldns.godaddy serial=1785651679

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-02.azure-dns.com2026-02-28 → 2026-08-02 · 3 obs

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

○NSns1.msft.net2015-05-23 → 2017-03-18 · 4 obs

● 2015-05-23 03:51:14
● 2017-03-18 15:05:14
○ 2026-02-28 16:35:52
○ 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

○NSns2.msft.net2015-05-23 → 2017-03-18 · 4 obs

● 2015-05-23 03:51:14
● 2017-03-18 15:05:14
○ 2026-02-28 16:35:52
○ 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

○NSns3.msft.net2015-05-23 → 2017-03-18 · 4 obs

● 2015-05-23 03:51:14
● 2017-03-18 15:05:14
○ 2026-02-28 16:35:52
○ 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

○NSns4.msft.net2015-05-23 → 2017-03-18 · 4 obs

● 2015-05-23 03:51:14
● 2017-03-18 15:05:14
○ 2026-02-28 16:35:52
○ 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

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

○ 2017-03-18 15:05:14
● 2026-02-28 16:35:52
● 2026-08-02 06:48:00

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

○ 2016-05-05 16:47:26
● 2017-03-18 15:05:14
○ 2026-02-28 16:35:52
○ 2026-08-02 06:48:00

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

○ 2016-05-05 16:47:26
● 2017-03-18 15:05:14
○ 2026-02-28 16:35:52
○ 2026-08-02 06:48:00

○A64.4.6.1002015-05-23 → 2016-05-05 · 4 obs

● 2015-05-23 03:51:14
● 2016-05-05 16:47:26
○ 2017-03-18 15:05:14
○ 2026-08-02 06:48:00

○A65.55.39.102015-05-23 → 2016-05-05 · 4 obs

● 2015-05-23 03:51:14
● 2016-05-05 16:47:26
○ 2017-03-18 15:05:14
○ 2026-08-02 06:48:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
us	x.cctld.us, f.cctld.us, b.cctld.us, m.cctld.us...	-
secure-microsoft.us	ns1-02.azure-dns.com, ns3-02.azure-dns.org, ns2-02.azure-dns.net, ns4-02.azure-dns.info	-

✅ Authoritative Response

Server:208.84.5.2

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 614ms | 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`

Analysis

IP Addresses

secure-microsoft.us directs to five IP numbers, including 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others

binggleek.com, dotnetlang.net, microsoftbiconference.net plus two other host names have IP numbers in common with secure-microsoft.us.

Name Servers

Four name servers handle the delegation for secure-microsoft.us: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

secure-microsoft.us partially shares its NS delegation with several other domains, including hospitaldaluz.pt, finiato.com, lynctext.com and two others.

ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org each carry two IP addresses. ns1-02.azure-dns.com has 13.107.236.2 and 2603:1061:0:700::2; ns4-02.azure-dns.info has 208.84.5.2 and 2620:1ec:bda:700::2; ns2-02.azure-dns.net has 150.171.21.2 and 2620:1ec:8ec:700::2; ns3-02.azure-dns.org has 204.14.183.2 and 2a01:111:4000:700::2.