`microsoftband.fail`

DNSSEC	⚠️ Not signed
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}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
TXT	`v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.aga...`
SOA	`ns1-01.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`fail`

	DNSSEC	🔒 Signed (DS record present)
	NS	`v0n0.nic.fail` ⭐
	NS	`v0n1.nic.fail`
	NS	`v0n2.nic.fail`
	NS	`v0n3.nic.fail`
	NS	`v2n0.nic.fail`
	NS	`v2n1.nic.fail`
	SOA	`v0n0.nic.fail`hostmaster@donuts.email serial=1774295722

Same first word

DNS History

6 records (4 active, 2 former)

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

● 2026-02-28 13:27:00
● 2026-03-23 21:39:44

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

● 2026-02-28 13:27:00
● 2026-03-23 21:39:44

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

● 2026-02-28 13:27:00
● 2026-03-23 21:39:44

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

● 2026-02-28 13:27:00
● 2026-03-23 21:39:44

○A64.4.6.2332016-12-10 → 2016-12-10 · 3 obs

● 2016-12-10 21:54:50
○ 2026-02-28 13:27:00
○ 2026-03-23 21:39:44

○A65.55.39.122016-12-10 → 2016-12-10 · 3 obs

● 2016-12-10 21:54:50
○ 2026-02-28 13:27:00
○ 2026-03-23 21:39:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
fail	v0n0.nic.fail, v2n0.nic.fail, v0n2.nic.fail, v2n1.nic.fail...	12 records
microsoftband.fail	ns3-01.azure-dns.org, ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns4-01.azure-dns.info	-

✅ Authoritative Response

Server:208.84.5.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsoftband.fail (unsigned zone)

⏱️ Timing

Total: 862ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
TXT	1	`v=DMARC1; p=reject; pct=100; rua=mailto:`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n0.nic.fail, v0n0.nic.fail, v2n0.nic.fail...)

Analysis

Name Servers

microsoftband.fail delegates to four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

microsoftband.fail at least partially shares name servers with other domains, including at-home.co.in, flyhalifax.ca, limolinkreservations.com, muottasmuragl.ch and ocalc.com.

Host names with two IP numbers: ns1-01.azure-dns.com points to 2603:1061:0:700::1 and 13.107.236.1; ns4-01.azure-dns.info points to 2620:1ec:bda:700::1 and 208.84.5.1; ns2-01.azure-dns.net points to 2620:1ec:8ec:700::1 and 150.171.21.1; ns3-01.azure-dns.org points to 2a01:111:4000:700::1 and 204.14.183.1.

microsoftband.fail - robtex.com