`crowdcoverage.com`

DNSSEC	⚠️ Not signed
A	13.56.33.8^{🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix}
		PTR	`ec2-13-56-33-8.us-west-1.compute.amazonaws.com`
NS	`ns1.brandbucket.com` ⭐
		A	2600:1f1c:800:8b01:2ba3:bb61:44fb:b361^{🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS}
		A	54.241.53.41^{🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix}
			PTR	`ec2-54-241-53-41.us-west-1.compute.amazonaws.com`
NS	`ns2.brandbucket.com`
		A	2600:1f16:54:8701:4012:7e34:5c5f:95a8^{🇺🇸 Amazon2600:1f16::/38 AMAZON AWS}
		A	18.221.52.246^{🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix}
			PTR	`ec2-18-221-52-246.us-east-2.compute.amazonaws.com`
TXT	`afternic-verification-cvgUQU8SkLxsjXcPBSk2CM`
TXT	`27aab5373841b85aab94982ee19ab62f96481ed6`
TXT	`v=spf1 -all`
SOA	`ns1.brandbucket.com`mail@crowdcoverage.com 2026-01-24 #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=1774576977

Same first word

crowdcoverage.com

DNS History

9 records (3 active, 6 former)

●NSns1.brandbucket.com2026-03-27 → 2026-03-27 · 2 obs

○ 2017-01-30 07:15:16
● 2026-03-27 02:10:20

●NSns2.brandbucket.com2026-03-27 → 2026-03-27 · 2 obs

○ 2017-01-30 07:15:16
● 2026-03-27 02:10:20

○NSns37.domaincontrol.com2015-06-24 → 2017-01-30 · 3 obs

● 2015-06-24 23:27:22
● 2017-01-30 07:15:16
○ 2026-03-27 02:10:20

○NSns38.domaincontrol.com2015-06-24 → 2017-01-30 · 3 obs

● 2015-06-24 23:27:22
● 2017-01-30 07:15:16
○ 2026-03-27 02:10:20

○MXmailstore1.secureserver.net2015-06-24 → 2017-01-30 · 3 obs

● 2015-06-24 23:27:22
● 2017-01-30 07:15:16
○ 2026-03-27 02:10:20

○MXsmtp.secureserver.net2015-06-24 → 2017-01-30 · 3 obs

● 2015-06-24 23:27:22
● 2017-01-30 07:15:16
○ 2026-03-27 02:10:20

●A13.56.33.82026-03-27 → 2026-03-27 · 2 obs

○ 2018-08-03 07:07:48
● 2026-03-27 02:10:20

○A184.168.137.12015-06-24 → 2017-01-30 · 4 obs

● 2015-06-24 23:27:22
● 2017-01-30 07:15:16
○ 2018-08-03 07:07:48
○ 2026-03-27 02:10:20

○A185.42.173.2482018-08-03 → 2018-08-03 · 3 obs

○ 2017-01-30 07:15:16
● 2018-08-03 07:07:48
○ 2026-03-27 02:10:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
crowdcoverage.com	ns1.brandbucket.com, ns2.brandbucket.com	2 records

✅ Authoritative Response

Server:54.241.53.41

NS records: ns1.brandbucket.com, ns2.brandbucket.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for crowdcoverage.com (unsigned zone)

⏱️ Timing

Total: 333ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`13.56.33.8`
NS	2	`ns2.brandbucket.com, ns1.brandbucket.com`
TXT	3	`afternic-verification-cvgUQU8SkLxsjXcPBS, 27aab5373841b85aab94982ee19ab62f96481ed6...`
SOA	1	`ns1.brandbucket.com mail.crowdcoverage.c`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)

Analysis

IP Addresses

crowdcoverage.com points to a single IP number: 13.56.33.8.

Other host names, for instance xoowe.com, wildcanna.com, genegate.com, viditron.com and jixoy.com share IP numbers with crowdcoverage.com.

Name Servers

crowdcoverage.com is delegated to two name servers: ns1.brandbucket.com and ns2.brandbucket.com.

crowdcoverage.com uses the same name server setup as other domains, for instance fuvor.com, megaxy.com, anloo.com, vabago.com and sizene.com.

crowdcoverage.com partially shares name servers with other domains, for instance fungophile.com.

these name servers are often used together with the name servers verification-z5atyvddcsxaefgezfdzrc.ns101.verify.hn.

Host names with two IP numbers:

The host ns1.brandbucket.com points to 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361 and 54.241.53.41.

The host ns2.brandbucket.com points to 2600:1f16:54:8701:4012:7e34:5c5f:95a8 and 18.221.52.246.

crowdcoverage.com - robtex.com