`botdetection.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns03.domaincontrol.com` ⭐
		A	2603:5:2150::2^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns03.domaincontrol.com`
		A	97.74.101.2^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns03.domaincontrol.com`
NS	`ns04.domaincontrol.com`
		A	2603:5:2250::2^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns04.domaincontrol.com`
		A	173.201.69.2^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns04.domaincontrol.com`
SOA	`ns03.domaincontrol.com`dns@jomax.net 2025-04-15 #0

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

Same first word

botdetection.com

DNS History

6 records (4 active, 2 former)

●NSns03.domaincontrol.com2026-03-01 → 2026-03-21 · 2 obs

● 2026-03-01 19:15:42
● 2026-03-21 02:07:00

●NSns04.domaincontrol.com2026-03-01 → 2026-03-21 · 2 obs

● 2026-03-01 19:15:42
● 2026-03-21 02:07:00

●A15.197.148.332026-03-01 → 2026-03-21 · 3 obs

○ 2020-02-06 21:36:52
● 2026-03-01 19:15:42
● 2026-03-21 02:07:00

○A207.148.248.1432015-11-06 → 2020-02-06 · 5 obs

○ 2015-06-27 15:07:40
● 2015-11-06 05:11:34
● 2020-02-06 21:36:52
○ 2026-03-01 19:15:42
○ 2026-03-21 02:07:00

●A3.33.130.1902026-03-01 → 2026-03-21 · 3 obs

○ 2020-02-06 21:36:52
● 2026-03-01 19:15:42
● 2026-03-21 02:07:00

○A66.151.181.492015-06-27 → 2015-06-27 · 3 obs

● 2015-06-27 15:07:40
○ 2015-11-06 05:11:34
○ 2026-03-21 02:07:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
botdetection.com	ns03.domaincontrol.com, ns04.domaincontrol.com	4 records

✅ Authoritative Response

Server: 173.201.69.2

NS records: ns03.domaincontrol.com, ns04.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for botdetection.com (unsigned zone)

⏱️ Timing

Total: 363ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns03.domaincontrol.com, ns04.domaincontrol.com`
SOA	1	`ns03.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns03.domaincontrol.com, ns03.domaincontrol.com, ns04.domaincontrol.com...)

Analysis

IP Addresses

botdetection.com resolves to two IP numbers: 3.33.130.190 and 15.197.148.33.

Other host names, for instance uplifterz.com, designliftoff.com, onlinemusicawards.org, saigonline.com and bithunt.com share IP numbers with botdetection.com.

Name Servers

Two name servers ns03.domaincontrol.com and ns04.domaincontrol.com handle delegation for botdetection.com.

botdetection.com uses the same name server setup as other domains, for example bregliolaw.com, amandaghost.com, kenkotler.com, brittanygraham-soprano.com and roehrconsultingllc.com.

Host names with two IP numbers:

ns03.domaincontrol.com points to: 2603:5:2150::2 and 97.74.101.2

ns04.domaincontrol.com points to: 2603:5:2250::2 and 173.201.69.2

botdetection.com - robtex.com