microsoftsecuritycenter.com - dns.ninja

`microsoftsecuritycenter.com`

DNSSEC	⚠️ Not signed
A	20.70.246.20^{🇦🇺 Microsoft20.64.0.0/10}
		PTR	`ip-20-70-246-20.defastlink.net`
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=1780546989

Same first word

microsoftsecuritycenter.com

DNS History

19 records (9 active, 10 former)

●NSns1-02.azure-dns.com2026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

○NSns1.msft.net2015-08-05 → 2018-11-20 · 4 obs

● 2015-08-05 14:41:56
● 2018-11-20 03:47:20
○ 2026-03-01 12:12:46
○ 2026-06-04 04:35:58

●NSns2-02.azure-dns.net2026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

○NSns2.msft.net2015-08-05 → 2018-11-20 · 4 obs

● 2015-08-05 14:41:56
● 2018-11-20 03:47:20
○ 2026-03-01 12:12:46
○ 2026-06-04 04:35:58

●NSns3-02.azure-dns.org2026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

○NSns3.msft.net2015-08-05 → 2018-11-20 · 4 obs

● 2015-08-05 14:41:56
● 2018-11-20 03:47:20
○ 2026-03-01 12:12:46
○ 2026-06-04 04:35:58

●NSns4-02.azure-dns.info2026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

○NSns4.msft.net2015-08-05 → 2018-11-20 · 4 obs

● 2015-08-05 14:41:56
● 2018-11-20 03:47:20
○ 2026-03-01 12:12:46
○ 2026-06-04 04:35:58

○A104.215.95.1872018-11-20 → 2018-11-20 · 4 obs

○ 2017-02-10 18:33:08
● 2018-11-20 03:47:20
○ 2026-03-01 12:12:46
○ 2026-06-04 04:35:58

●A20.112.250.1332026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

●A20.231.239.2462026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

●A20.236.44.1622026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

●A20.70.246.202026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

●A20.76.201.1712026-03-01 → 2026-06-04 · 3 obs

○ 2018-11-20 03:47:20
● 2026-03-01 12:12:46
● 2026-06-04 04:35:58

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

○ 2016-06-26 03:00:24
● 2017-02-10 18:33:08
○ 2018-11-20 03:47:20
○ 2026-06-04 04:35:58

○A52.164.206.562018-11-20 → 2018-11-20 · 4 obs

○ 2017-02-10 18:33:08
● 2018-11-20 03:47:20
○ 2026-03-01 12:12:46
○ 2026-06-04 04:35:58

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

○ 2016-06-26 03:00:24
● 2017-02-10 18:33:08
○ 2018-11-20 03:47:20
○ 2026-06-04 04:35:58

○A64.4.6.1002015-08-05 → 2016-06-26 · 4 obs

● 2015-08-05 14:41:56
● 2016-06-26 03:00:24
○ 2017-02-10 18:33:08
○ 2026-06-04 04:35:58

○A65.55.39.102015-08-05 → 2016-06-26 · 4 obs

● 2015-08-05 14:41:56
● 2016-06-26 03:00:24
○ 2017-02-10 18:33:08
○ 2026-06-04 04:35:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
microsoftsecuritycenter.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:208.84.5.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 microsoftsecuritycenter.com (unsigned zone)

⏱️ Timing

Total: 530ms | 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

microsoftsecuritycenter.com points to 5 IP numbers: 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others.

Additional host names — micosoft.co.uk, xboxaustralia.com, microsoft-sharepoint.com and two others — share IP numbers with microsoftsecuritycenter.com.

Name Servers

microsoftsecuritycenter.com is served by 4 authoritative name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

microsoftsecuritycenter.com has at least partial name server overlap with other domains, such as rubycogan.com, freedvdplayer.org, aw-lab.be and two others.

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