`microsofthololens.tw`

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

`tw`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.dns.tw` ⭐
	NS	`anytld.apnic.net`
	NS	`b.dns.tw`
	NS	`c.dns.tw`
	NS	`d.dns.tw`
	NS	`e.dns.tw`
	NS	`f.dns.tw`
	NS	`g.dns.tw`
	NS	`h.dns.tw` 🔒
	SOA	`a.dns.tw`snw@twnic.net.tw serial=2010991523

Same first word

DNS History

9 records (9 active, 0 former)

●NSns1-09.azure-dns.com2026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●NSns2-09.azure-dns.net2026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●NSns3-09.azure-dns.org2026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●NSns4-09.azure-dns.info2026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●A20.112.250.1332026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●A20.231.239.2462026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●A20.236.44.1622026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●A20.70.246.202026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

●A20.76.201.1712026-02-28 → 2026-03-09 · 2 obs

● 2026-02-28 13:27:52
● 2026-03-09 09:58:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tw	b.dns.tw, f.dns.tw, e.dns.tw, h.dns.tw...	-
microsofthololens.tw	ns4-09.azure-dns.info, ns2-09.azure-dns.net, ns1-09.azure-dns.com, ns3-09.azure-dns.org	-

✅ Authoritative Response

Server: 204.14.183.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsofthololens.tw (unsigned zone)

⏱️ Timing

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

Analysis

IP Addresses

Five IP numbers are pointed to by microsofthololens.tw: 20.70.246.20, 20.76.201.171, 20.112.250.133, 20.231.239.246 and 20.236.44.162.

other host names including halosoftware.com, webmatrix.com, silverlight.jo, xn--skyp-jpa.biz and sharepointapps.net share IP numbers with microsofthololens.tw.

Name Servers

microsofthololens.tw is delegated 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.

microsofthololens.tw at least partially shares name servers with other domains, for instance manufacturingoperations.com, ipchydro.org, bingnetwork.ru, sapin.fi and gardotrans.com.

Host names with two IP numbers:

ns1-09.azure-dns.com points to 2603:1061:0:700::9 and 13.107.236.9; ns4-09.azure-dns.info points to 2620:1ec:bda:700::9 and 208.84.5.9; ns2-09.azure-dns.net points to 2620:1ec:8ec:700::9 and 150.171.21.9; ns3-09.azure-dns.org points to 2a01:111:4000:700::9 and 204.14.183.9.

microsofthololens.tw - robtex.com