hackercrowd.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`hackercrowd.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	`27aab5373841b85aab94982ee19ab62f96481ed6`
TXT	`v=spf1 -all`
TXT	`afternic-verification-cvgUQU8SkLxsjXcPBSk2CM`
SOA	`ns1.brandbucket.com`mail@hackercrowd.com 2024-03-05 #2

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

Same first word

hackercrowd.com

Similar names

crowdhacker.com

crowdhacker.us

Previous names

Next names

DNS History

21 records (3 active, 18 former)

○NSbuy.internettraffic.com2015-11-21 → 2015-11-21 · 4 obs

○ 2015-07-12 09:24:20
● 2015-11-21 23:10:08
○ 2016-03-06 04:19:32
○ 2026-08-30 18:01:04

○NSdocks12.rzone.de2015-07-12 → 2015-07-12 · 3 obs

● 2015-07-12 09:24:20
○ 2015-11-21 23:10:08
○ 2026-08-30 18:01:04

○NSlocalhost2016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○NSns1.bodis.com2016-06-30 → 2016-06-30 · 4 obs

○ 2016-03-06 04:19:32
● 2016-06-30 09:34:18
○ 2020-02-11 11:41:56
○ 2026-08-30 18:01:04

●NSns1.brandbucket.com2020-02-11 → 2026-08-30 · 3 obs

○ 2016-06-30 09:34:18
● 2020-02-11 11:41:56
● 2026-08-30 18:01:04

○NSns1.pheenixdns.com2016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○NSns2.bodis.com2016-06-30 → 2016-06-30 · 4 obs

○ 2016-03-06 04:19:32
● 2016-06-30 09:34:18
○ 2020-02-11 11:41:56
○ 2026-08-30 18:01:04

●NSns2.brandbucket.com2020-02-11 → 2026-08-30 · 3 obs

○ 2016-06-30 09:34:18
● 2020-02-11 11:41:56
● 2026-08-30 18:01:04

○NSns2.pheenixdns.com2016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○NSns3.pheenixdns.com2016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○NSns4.pheenixdns.com2016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○NSsell.internettraffic.com2015-11-21 → 2015-11-21 · 4 obs

○ 2015-07-12 09:24:20
● 2015-11-21 23:10:08
○ 2016-03-06 04:19:32
○ 2026-08-30 18:01:04

○NSshades03.rzone.de2015-07-12 → 2015-07-12 · 3 obs

● 2015-07-12 09:24:20
○ 2015-11-21 23:10:08
○ 2026-08-30 18:01:04

○A122.248.252.552016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

●A13.56.33.82020-02-11 → 2026-08-30 · 3 obs

○ 2017-03-31 15:51:04
● 2020-02-11 11:41:56
● 2026-08-30 18:01:04

○A199.59.243.1202016-06-30 → 2016-06-30 · 4 obs

○ 2016-03-06 04:19:32
● 2016-06-30 09:34:18
○ 2017-03-31 15:51:04
○ 2026-08-30 18:01:04

○A54.183.99.632017-03-31 → 2017-03-31 · 4 obs

○ 2016-06-30 09:34:18
● 2017-03-31 15:51:04
○ 2020-02-11 11:41:56
○ 2026-08-30 18:01:04

○A54.232.126.1092016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○A54.243.196.2462016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○A54.247.71.2442016-03-06 → 2016-03-06 · 4 obs

○ 2015-11-21 23:10:08
● 2016-03-06 04:19:32
○ 2016-06-30 09:34:18
○ 2026-08-30 18:01:04

○A69.172.201.2082015-11-21 → 2015-11-21 · 3 obs

● 2015-11-21 23:10:08
○ 2016-03-06 04:19:32
○ 2026-08-30 18:01:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net...	-
hackercrowd.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 hackercrowd.com (unsigned zone)

⏱️ Timing

Total: 351ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`13.56.33.8`
NS	2	`ns1.brandbucket.com, ns2.brandbucket.com`
TXT	3	`27aab5373841b85aab94982ee19ab62f96481ed6, v=spf1 -all...`
SOA	1	`ns1.brandbucket.com mail.hackercrowd.com`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

hackercrowd.com resolves to one IP address: 13.56.33.8.

puratia.com, synectico.com, stackspectrum.com and two other host names share IP numbers with hackercrowd.com.

Name Servers

hackercrowd.com uses two name servers for its delegation: ns1.brandbucket.com and ns2.brandbucket.com.

hackercrowd.com uses the same name servers as several other domains — among them zaloti.com, blurte.com, strivesuite.com and two more.

At least some of hackercrowd.com's name servers are also used by other domains, among them creatingcloud.com.

The two host names ns1.brandbucket.com and ns2.brandbucket.com each have a pair of IP addresses: ns1.brandbucket.com has 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361, and ns2.brandbucket.com has 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8.