`supportresponse.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	`v=spf1 -all`
TXT	`27aab5373841b85aab94982ee19ab62f96481ed6`
SOA	`ns1.brandbucket.com`mail@supportresponse.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=1774527857

Same first word

supportresponse.com

DNS History

8 records (3 active, 5 former)

○NSdns1.softhosting.com2007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 16:36:30
○ 2015-07-04 22:10:42
○ 2026-03-26 12:38:26

○NSdns2.softhosting.com2007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 16:36:30
○ 2015-07-04 22:10:42
○ 2026-03-26 12:38:26

○NSdns3.softhosting.com2007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 16:36:30
○ 2015-07-04 22:10:42
○ 2026-03-26 12:38:26

●NSns1.brandbucket.com2026-03-14 → 2026-03-26 · 3 obs

○ 2015-07-04 22:10:42
● 2026-03-14 22:51:32
● 2026-03-26 12:38:26

●NSns2.brandbucket.com2026-03-14 → 2026-03-26 · 3 obs

○ 2015-07-04 22:10:42
● 2026-03-14 22:51:32
● 2026-03-26 12:38:26

○MXmail.elitehost.com2007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 16:36:30
○ 2015-07-04 22:10:42
○ 2026-03-26 12:38:26

●A13.56.33.82026-03-14 → 2026-03-26 · 3 obs

○ 2015-07-04 22:10:42
● 2026-03-14 22:51:32
● 2026-03-26 12:38:26

○A208.179.177.312007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 16:36:30
○ 2015-07-04 22:10:42
○ 2026-03-26 12:38:26

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:18.221.52.246

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for supportresponse.com (unsigned zone)

⏱️ Timing

Total: 154ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`13.56.33.8`
NS	2	`ns1.brandbucket.com, ns2.brandbucket.com`
TXT	3	`afternic-verification-cvgUQU8SkLxsjXcPBS, v=spf1 -all...`
SOA	1	`ns1.brandbucket.com mail.supportresponse`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

supportresponse.com points to a single IP address: 13.56.33.8.

Other host names such as nobledelight.com, harbora.com, programyourbrain.com, vesry.com and feetall.com share IPs with supportresponse.com.

Name Servers

Two name servers ns1.brandbucket.com and ns2.brandbucket.com handle the delegation for supportresponse.com.

supportresponse.com shares the same name server setup as other domains, for example precine.com, nucleargear.com, chefstatus.com, innovasync.com and drexxo.com.

supportresponse.com shares name servers with other domains at least partially, for instance yakitty.com.

Host names with two IP numbers:

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.

supportresponse.com - robtex.com