microsofthyper-v.in - dns.ninja

`microsofthyper-v.in`

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

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns1.registry.in` ⚠️ Not in parent delegation
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	NS	`ns2.registry.in` ⚠️ Not in parent delegation
	NS	`ns3.registry.in` ⚠️ Not in parent delegation
	NS	`ns4.registry.in` ⚠️ Not in parent delegation
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1780705258

Same first word

DNS History

19 records (9 active, 10 former)

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

○NSns1.msft.net2015-07-16 → 2020-01-05 · 4 obs

● 2015-07-16 02:35:40
● 2020-01-05 03:11:28
○ 2026-02-28 10:51:02
○ 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

○NSns2.msft.net2015-07-16 → 2020-01-05 · 4 obs

● 2015-07-16 02:35:40
● 2020-01-05 03:11:28
○ 2026-02-28 10:51:02
○ 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

○NSns3.msft.net2015-07-16 → 2020-01-05 · 4 obs

● 2015-07-16 02:35:40
● 2020-01-05 03:11:28
○ 2026-02-28 10:51:02
○ 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

○NSns4.msft.net2015-07-16 → 2020-01-05 · 4 obs

● 2015-07-16 02:35:40
● 2020-01-05 03:11:28
○ 2026-02-28 10:51:02
○ 2026-06-06 00:26:16

○A104.215.95.1872020-01-05 → 2020-01-05 · 4 obs

○ 2017-01-23 08:52:54
● 2020-01-05 03:11:28
○ 2026-02-28 10:51:02
○ 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

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

○ 2020-01-05 03:11:28
● 2026-02-28 10:51:02
● 2026-06-06 00:26:16

○A40.84.199.2332017-01-23 → 2017-01-23 · 4 obs

○ 2016-04-29 08:43:12
● 2017-01-23 08:52:54
○ 2020-01-05 03:11:28
○ 2026-06-06 00:26:16

○A52.164.206.562020-01-05 → 2020-01-05 · 4 obs

○ 2017-01-23 08:52:54
● 2020-01-05 03:11:28
○ 2026-02-28 10:51:02
○ 2026-06-06 00:26:16

○A52.178.167.1092017-01-23 → 2017-01-23 · 4 obs

○ 2016-04-29 08:43:12
● 2017-01-23 08:52:54
○ 2020-01-05 03:11:28
○ 2026-06-06 00:26:16

○A64.4.6.1002015-07-16 → 2016-04-29 · 4 obs

● 2015-07-16 02:35:40
● 2016-04-29 08:43:12
○ 2017-01-23 08:52:54
○ 2026-06-06 00:26:16

○A65.55.39.102015-07-16 → 2016-04-29 · 4 obs

● 2015-07-16 02:35:40
● 2016-04-29 08:43:12
○ 2017-01-23 08:52:54
○ 2026-06-06 00:26:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
microsofthyper-v.in	ns2-01.azure-dns.net, ns4-01.azure-dns.info, ns1-01.azure-dns.com, ns3-01.azure-dns.org	-

✅ Authoritative Response

Server:204.14.183.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsofthyper-v.in (unsigned zone)

⏱️ Timing

Total: 639ms | Queries: -

📄 Records

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

Analysis

IP Addresses

With 5 IP numbers in total, microsofthyper-v.in directs to 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others.

Among the host names that share IP numbers with microsofthyper-v.in are prompt-flow.ms, feedsync.org, bingeseller.com and two others.

Name Servers

DNS for microsofthyper-v.in is handled by 4 name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

At least some of microsofthyper-v.in's name servers are shared with other domains, for example microsoft.co, swatch007villains.com, monroecounty-fl.gov and two more.

Four hostnames, each resolving to a pair of IP addresses: ns1-01.azure-dns.com directs to 13.107.236.1 and 2603:1061:0:700::1; ns4-01.azure-dns.info directs to 208.84.5.1 and 2620:1ec:bda:700::1; ns2-01.azure-dns.net directs to 150.171.21.1 and 2620:1ec:8ec:700::1; ns3-01.azure-dns.org directs to 204.14.183.1 and 2a01:111:4000:700::1.