`audiencecommunity.com`

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

Same first word

audiencecommunity.com

DNS History

7 records (4 active, 3 former)

●NSns1-33.azure-dns.com2026-02-28 → 2026-03-24 · 3 obs

○ 2019-04-27 18:46:30
● 2026-02-28 18:21:38
● 2026-03-24 21:04:48

●NSns2-33.azure-dns.net2026-02-28 → 2026-03-24 · 3 obs

○ 2019-04-27 18:46:30
● 2026-02-28 18:21:38
● 2026-03-24 21:04:48

●NSns3-33.azure-dns.org2026-02-28 → 2026-03-24 · 3 obs

○ 2019-04-27 18:46:30
● 2026-02-28 18:21:38
● 2026-03-24 21:04:48

●NSns4-33.azure-dns.info2026-02-28 → 2026-03-24 · 3 obs

○ 2019-04-27 18:46:30
● 2026-02-28 18:21:38
● 2026-03-24 21:04:48

○NSns57.domaincontrol.com2019-04-27 → 2019-04-27 · 3 obs

● 2019-04-27 18:46:30
○ 2026-02-28 18:21:38
○ 2026-03-24 21:04:48

○NSns58.domaincontrol.com2019-04-27 → 2019-04-27 · 3 obs

● 2019-04-27 18:46:30
○ 2026-02-28 18:21:38
○ 2026-03-24 21:04:48

○A50.63.202.332019-04-27 → 2019-04-27 · 3 obs

● 2019-04-27 18:46:30
○ 2026-02-28 18:21:38
○ 2026-03-24 21:04:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
audiencecommunity.com	ns3-33.azure-dns.org, ns4-33.azure-dns.info, ns1-33.azure-dns.com, ns2-33.azure-dns.net	2 records

✅ Authoritative Response

Server:150.171.16.33

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for audiencecommunity.com (unsigned zone)

⏱️ Timing

Total: 223ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

audiencecommunity.com's delegation is handled by four name servers: ns1-33.azure-dns.com, ns4-33.azure-dns.info, ns2-33.azure-dns.net and ns3-33.azure-dns.org.

audiencecommunity.com partially shares name servers with other domains; examples include vipps.org, uranai-plus.com, amger.pro, astarita.com.br and eastus-01.azurewebsites.net.

Host names with two IPs:

ns1-33.azure-dns.com points to 2603:1061:0:10::21 and 150.171.10.33

ns4-33.azure-dns.info points to 2620:1ec:bda:10::21 and 13.107.206.33

ns2-33.azure-dns.net points to 2620:1ec:8ec:10::21 and 150.171.16.33

ns3-33.azure-dns.org points to 2a01:111:4000:10::21 and 13.107.222.33

audiencecommunity.com - robtex.com