`watchtowercluster.com`

DNSSEC	⚠️ Not signed
NS	`ns1-36.azure-dns.com` ⭐
		A	2603:1061:0:10::24^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
		A	150.171.10.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
NS	`ns2-36.azure-dns.net`
		A	2620:1ec:8ec:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
		A	150.171.16.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
NS	`ns3-36.azure-dns.org`
		A	2a01:111:4000:10::24^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-36.azure-dns.org`
		A	13.107.222.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-36.azure-dns.org`
NS	`ns4-36.azure-dns.info`
		A	2620:1ec:bda:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
		A	13.107.206.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
SOA	`ns1-36.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=1778340216

Same first word

watchtowercluster.com

DNS History

4 records (4 active, 0 former)

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

● 2026-02-28 15:49:30
● 2026-05-09 15:30:48

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

● 2026-02-28 15:49:30
● 2026-05-09 15:30:48

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

● 2026-02-28 15:49:30
● 2026-05-09 15:30:48

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

● 2026-02-28 15:49:30
● 2026-05-09 15:30:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, b.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net...	-
watchtowercluster.com	ns1-36.azure-dns.com, ns2-36.azure-dns.net, ns4-36.azure-dns.info, ns3-36.azure-dns.org	2 records

✅ Authoritative Response

Server:13.107.222.36

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for watchtowercluster.com (unsigned zone)

⏱️ Timing

Total: 352ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-36.azure-dns.com, ns2-36.azure-dns.net...`
SOA	1	`ns1-36.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

watchtowercluster.com is delegated to four name servers: ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net and ns3-36.azure-dns.org.

watchtowercluster.com at least partially shares its name servers with other domains, for instance cantelmedical.com, mobilepay.fi, mcafeetaft.net, planpay.se and africanalliance.sz.

These name servers are often used together with the name servers ns10.dnsmadeeasy.com.

Host names with two IPs: ns1-36.azure-dns.com points to 2603:1061:0:10::24 and 150.171.10.36; ns4-36.azure-dns.info points to 2620:1ec:bda:10::24 and 13.107.206.36; ns2-36.azure-dns.net points to 2620:1ec:8ec:10::24 and 150.171.16.36; ns3-36.azure-dns.org points to 2a01:111:4000:10::24 and 13.107.222.36.

watchtowercluster.com - robtex.com