microsoftstudiosblog.com - dns.ninja

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

Same first word

microsoftstudiosblog.net

microsoftstudiosblog.com

DNS History

19 records (9 active, 10 former)

●NSns1-05.azure-dns.com2026-02-28 → 2026-08-13 · 3 obs

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

○NSns1.msft.net2015-06-10 → 2018-09-26 · 4 obs

● 2015-06-10 16:38:46
● 2018-09-26 14:46:46
○ 2026-02-28 15:23:40
○ 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

○NSns2.msft.net2015-06-10 → 2018-09-26 · 4 obs

● 2015-06-10 16:38:46
● 2018-09-26 14:46:46
○ 2026-02-28 15:23:40
○ 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

○NSns3.msft.net2015-06-10 → 2018-09-26 · 4 obs

● 2015-06-10 16:38:46
● 2018-09-26 14:46:46
○ 2026-02-28 15:23:40
○ 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

○NSns4.msft.net2015-06-10 → 2018-09-26 · 4 obs

● 2015-06-10 16:38:46
● 2018-09-26 14:46:46
○ 2026-02-28 15:23:40
○ 2026-08-13 18:00:20

○A104.215.95.1872018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-06 21:26:12
● 2018-09-26 14:46:46
○ 2026-02-28 15:23:40
○ 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

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

○ 2018-09-26 14:46:46
● 2026-02-28 15:23:40
● 2026-08-13 18:00:20

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

○ 2016-04-26 12:04:58
● 2017-02-06 21:26:12
○ 2018-09-26 14:46:46
○ 2026-08-13 18:00:20

○A52.164.206.562018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-06 21:26:12
● 2018-09-26 14:46:46
○ 2026-02-28 15:23:40
○ 2026-08-13 18:00:20

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

○ 2016-04-26 12:04:58
● 2017-02-06 21:26:12
○ 2018-09-26 14:46:46
○ 2026-08-13 18:00:20

○A64.4.6.1002015-06-10 → 2016-04-26 · 4 obs

● 2015-06-10 16:38:46
● 2016-04-26 12:04:58
○ 2017-02-06 21:26:12
○ 2026-08-13 18:00:20

○A65.55.39.102015-06-10 → 2016-04-26 · 4 obs

● 2015-06-10 16:38:46
● 2016-04-26 12:04:58
○ 2017-02-06 21:26:12
○ 2026-08-13 18:00:20

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:150.171.21.5

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftstudiosblog.com (unsigned zone)

⏱️ Timing

Total: 411ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

microsoftstudiosblog.com directs to five IP numbers, including 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others

msn-mobile.org, copilotstudio.co.kr, outlook.microsoft.com plus two other host names have IP numbers in common with microsoftstudiosblog.com.

Name Servers

Four name servers handle the delegation for microsoftstudiosblog.com: ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org.

There is at least partial name server overlap between microsoftstudiosblog.com and other domains — ceed.io, flagstaff.sa.edu.au, quest-software.co.uk and two more among them.

All four hostnames — ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org — resolve to two IP numbers apiece: ns1-05.azure-dns.com to 13.107.236.5 and 2603:1061:0:700::5; ns4-05.azure-dns.info to 208.84.5.5 and 2620:1ec:bda:700::5; ns2-05.azure-dns.net to 150.171.21.5 and 2620:1ec:8ec:700::5; ns3-05.azure-dns.org to 204.14.183.5 and 2a01:111:4000:700::5.