`steadyremedy.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	`e698482e-dc42-43b0-81b6-91255326632c`
TXT	`afternic-verification-cvgUQU8SkLxsjXcPBSk2CM`
SOA	`ns1.brandbucket.com`mail@steadyremedy.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=1774673307

Same first word

steadyremedy.com

DNS History

3 records (3 active, 0 former)

●NSns1.brandbucket.com2026-02-25 → 2026-03-28 · 2 obs

● 2026-02-25 03:05:08
● 2026-03-28 04:50:38

●NSns2.brandbucket.com2026-02-25 → 2026-03-28 · 2 obs

● 2026-02-25 03:05:08
● 2026-03-28 04:50:38

●A13.56.33.82026-02-25 → 2026-03-28 · 2 obs

● 2026-02-25 03:05:08
● 2026-03-28 04:50:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, f.gtld-servers.net, l.gtld-servers.net, h.gtld-servers.net...	-
steadyremedy.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 steadyremedy.com (unsigned zone)

⏱️ Timing

Total: 221ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

steadyremedy.com resolves to one IP number: 13.56.33.8.

Other host names, for instance optista.com, enician.com, www.wumix.com, www.logicsurge.com and cybachi.com share IP numbers with steadyremedy.com.

Name Servers

steadyremedy.com's delegation uses two name servers: ns1.brandbucket.com and ns2.brandbucket.com.

steadyremedy.com uses the same name server setup as other domains, such as verabliss.com, modatools.com, adrava.com, rankiva.com and yukizo.com.

steadyremedy.com shares name servers with other domains at least partially, for example peakism.com and zovla.com.

These name servers are commonly used with verification-hdcjgvecjcbdts9g8gdy3k.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

steadyremedy.com - robtex.com