`battlebotics.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@battlebotics.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=1785613557

Same first word

battlebotics.com

DNS History

8 records (3 active, 5 former)

○NSns05.domaincontrol.com2016-12-17 → 2017-08-22 · 3 obs

● 2016-12-17 03:02:46
● 2017-08-22 05:20:14
○ 2026-08-01 19:56:08

○NSns06.domaincontrol.com2016-12-17 → 2017-08-22 · 3 obs

● 2016-12-17 03:02:46
● 2017-08-22 05:20:14
○ 2026-08-01 19:56:08

●NSns1.brandbucket.com2026-08-01 → 2026-08-01 · 2 obs

○ 2017-08-22 05:20:14
● 2026-08-01 19:56:08

●NSns2.brandbucket.com2026-08-01 → 2026-08-01 · 2 obs

○ 2017-08-22 05:20:14
● 2026-08-01 19:56:08

○MXmailstore1.secureserver.net2016-12-17 → 2017-08-22 · 3 obs

● 2016-12-17 03:02:46
● 2017-08-22 05:20:14
○ 2026-08-01 19:56:08

○MXsmtp.secureserver.net2016-12-17 → 2017-08-22 · 3 obs

● 2016-12-17 03:02:46
● 2017-08-22 05:20:14
○ 2026-08-01 19:56:08

●A13.56.33.82026-08-01 → 2026-08-01 · 2 obs

○ 2017-08-22 05:20:14
● 2026-08-01 19:56:08

○A52.10.63.2242016-12-17 → 2017-08-22 · 3 obs

● 2016-12-17 03:02:46
● 2017-08-22 05:20:14
○ 2026-08-01 19:56:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
battlebotics.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 battlebotics.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	3	`v=spf1 -all, 27aab5373841b85aab94982ee19ab62f96481ed6...`
SOA	1	`ns1.brandbucket.com mail.battlebotics.co`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

battlebotics.com resolves to just one IP address, 13.56.33.8.

Two other host names, along with sunarya.com, lumindo.com and pinxio.com, also share IP numbers with battlebotics.com.

Name Servers

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

battlebotics.com shares its NS records with other domains, for example yozola.com, gigachick.com, mapovo.com and two others.

ns1.brandbucket.com and ns2.brandbucket.com both carry two IP addresses. The A records for ns1.brandbucket.com are 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361; the A records for ns2.brandbucket.com are 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8.

battlebotics.com - robtex.com