`communitycache.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	`e698482e-dc42-43b0-81b6-91255326632c`
TXT	`27aab5373841b85aab94982ee19ab62f96481ed6`
TXT	`v=spf1 -all`
SOA	`ns1.brandbucket.com`mail@communitycache.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=1774755847

Same first word

communitycache.com

DNS History

20 records (3 active, 17 former)

●NSns1.brandbucket.com2026-02-23 → 2026-03-29 · 3 obs

○ 2019-02-14 15:17:18
● 2026-02-23 07:39:48
● 2026-03-29 04:10:46

○NSns1.hostinger-ar.com2015-10-29 → 2015-10-29 · 3 obs

● 2015-10-29 18:48:38
○ 2017-02-14 06:13:02
○ 2026-03-29 04:10:46

●NSns2.brandbucket.com2026-02-23 → 2026-03-29 · 3 obs

○ 2019-02-14 15:17:18
● 2026-02-23 07:39:48
● 2026-03-29 04:10:46

○NSns2.hostinger-ar.com2015-10-29 → 2015-10-29 · 3 obs

● 2015-10-29 18:48:38
○ 2017-02-14 06:13:02
○ 2026-03-29 04:10:46

○NSns3.hostinger-ar.com2015-10-29 → 2015-10-29 · 3 obs

● 2015-10-29 18:48:38
○ 2017-02-14 06:13:02
○ 2026-03-29 04:10:46

○NSns31.domaincontrol.com2019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○NSns32.domaincontrol.com2019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○NSns4.hostinger-ar.com2015-10-29 → 2015-10-29 · 3 obs

● 2015-10-29 18:48:38
○ 2017-02-14 06:13:02
○ 2026-03-29 04:10:46

○MXmx1.hostinger.com.ar2015-10-29 → 2015-10-29 · 3 obs

● 2015-10-29 18:48:38
○ 2017-02-14 06:13:02
○ 2026-03-29 04:10:46

●A13.56.33.82026-02-23 → 2026-03-29 · 3 obs

○ 2019-02-14 15:17:18
● 2026-02-23 07:39:48
● 2026-03-29 04:10:46

○A184.168.221.452019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A184.168.221.472019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A184.168.221.502019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A184.168.221.512019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A184.168.221.532019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A184.168.221.552019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A184.168.221.592019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A185.28.21.942015-10-29 → 2015-10-29 · 3 obs

● 2015-10-29 18:48:38
○ 2017-02-14 06:13:02
○ 2026-03-29 04:10:46

○A50.63.202.332019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

○A50.63.202.342019-02-14 → 2019-02-14 · 4 obs

○ 2017-02-14 06:13:02
● 2019-02-14 15:17:18
○ 2026-02-23 07:39:48
○ 2026-03-29 04:10:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, g.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net...	-
communitycache.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 communitycache.com (unsigned zone)

⏱️ Timing

Total: 262ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`13.56.33.8`
NS	2	`ns2.brandbucket.com, ns1.brandbucket.com`
TXT	4	`afternic-verification-cvgUQU8SkLxsjXcPBS, e698482e-dc42-43b0-81b6-91255326632c...`
SOA	1	`ns1.brandbucket.com mail.communitycache.`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

communitycache.com maps to IP address 13.56.33.8.

Other host names, for instance audiokey.com, ritziness.com, elitekeys.com, blazedepot.com and www.metrohorizon.com share IP numbers with communitycache.com.

Name Servers

Two name servers ns1.brandbucket.com and ns2.brandbucket.com are delegated to communitycache.com.

communitycache.com uses the same name server configuration as other domains, such as phonicwave.com, trevend.com, ravler.com, lowmojo.com and vantient.com.

communitycache.com shares name servers with other domains at least partially, for instance druph.com and attractsy.com.

these name servers are commonly used with the name servers verification-rxblvqitk2egm9g8uc3wnf.ns101.verify.hn.

Host names with two IPs:

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

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

communitycache.com - robtex.com