`queen-collective.com`

DNSSEC	⚠️ Not signed
A	20.8.36.152^{🇳🇱 Microsoft20.0.0.0/11 MICROSOFT}
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

`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=1783930467

Same first word

queen-collective.com

DNS History

5 records (5 active, 0 former)

●NSns1-09.azure-dns.com2026-06-21 → 2026-07-13 · 2 obs

● 2026-06-21 03:05:46
● 2026-07-13 08:37:56

●NSns2-09.azure-dns.net2026-06-21 → 2026-07-13 · 2 obs

● 2026-06-21 03:05:46
● 2026-07-13 08:37:56

●NSns3-09.azure-dns.org2026-06-21 → 2026-07-13 · 2 obs

● 2026-06-21 03:05:46
● 2026-07-13 08:37:56

●NSns4-09.azure-dns.info2026-06-21 → 2026-07-13 · 2 obs

● 2026-06-21 03:05:46
● 2026-07-13 08:37:56

●A20.8.36.1522026-06-21 → 2026-07-13 · 2 obs

● 2026-06-21 03:05:46
● 2026-07-13 08:37:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, g.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net...	-
queen-collective.com	ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for queen-collective.com (unsigned zone)

⏱️ Timing

Total: 683ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

queen-collective.com has exactly one IP address — 20.8.36.152.

tustips.cl, pgsampling.com, s-mag.com plus two other host names have IP numbers in common with queen-collective.com.

Name Servers

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

There is at least partial name server overlap between queen-collective.com and other domains — exhibit.co.nz, albionroadmotorco.com, rivier.edu and two more among them.

All four hostnames — ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org — resolve to two IP numbers apiece: ns1-09.azure-dns.com to 13.107.236.9 and 2603:1061:0:700::9; ns4-09.azure-dns.info to 208.84.5.9 and 2620:1ec:bda:700::9; ns2-09.azure-dns.net to 150.171.21.9 and 2620:1ec:8ec:700::9; ns3-09.azure-dns.org to 204.14.183.9 and 2a01:111:4000:700::9.

queen-collective.com - robtex.com