`aggressivecbdregiment.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	`ns33.domaincontrol.com` ⭐
		A	2603:5:21a1::11^{🇺🇸 GODADDY-DNS2603:5:21a0::/44}
			PTR	`ns33.domaincontrol.com`
		A	97.74.106.17^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns33.domaincontrol.com`
NS	`ns34.domaincontrol.com`
		A	2603:5:22a1::11^{🇺🇸 GODADDY-DNS2603:5:22a0::/44}
			PTR	`ns34.domaincontrol.com`
		A	173.201.74.17^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns34.domaincontrol.com`
SOA	`ns33.domaincontrol.com`dns@jomax.net 2026-01-23 #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=1774768762

Same first word

aggressivecbdregiment.com

DNS History

7 records (4 active, 3 former)

○NSns1.afternic.com2016-12-17 → 2018-06-04 · 4 obs

● 2016-12-17 06:50:04
● 2018-06-04 12:59:04
○ 2026-02-20 03:36:28
○ 2026-03-29 07:26:12

○NSns2.afternic.com2016-12-17 → 2018-06-04 · 4 obs

● 2016-12-17 06:50:04
● 2018-06-04 12:59:04
○ 2026-02-20 03:36:28
○ 2026-03-29 07:26:12

●NSns33.domaincontrol.com2026-02-20 → 2026-03-29 · 3 obs

○ 2018-06-04 12:59:04
● 2026-02-20 03:36:28
● 2026-03-29 07:26:12

●NSns34.domaincontrol.com2026-02-20 → 2026-03-29 · 3 obs

○ 2018-06-04 12:59:04
● 2026-02-20 03:36:28
● 2026-03-29 07:26:12

●A15.197.148.332026-02-20 → 2026-03-29 · 3 obs

○ 2018-06-04 12:59:04
● 2026-02-20 03:36:28
● 2026-03-29 07:26:12

○A184.168.221.1042016-12-17 → 2018-06-04 · 4 obs

● 2016-12-17 06:50:04
● 2018-06-04 12:59:04
○ 2026-02-20 03:36:28
○ 2026-03-29 07:26:12

●A3.33.130.1902026-02-20 → 2026-03-29 · 3 obs

○ 2018-06-04 12:59:04
● 2026-02-20 03:36:28
● 2026-03-29 07:26:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net...	-
aggressivecbdregiment.com	ns33.domaincontrol.com, ns34.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.74.17

NS records: ns33.domaincontrol.com, ns34.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for aggressivecbdregiment.com (unsigned zone)

⏱️ Timing

Total: 167ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns33.domaincontrol.com, ns33.domaincontrol.com, ns34.domaincontrol.com...)

Analysis

IP Addresses

aggressivecbdregiment.com has two IP numbers: 3.33.130.190 and 15.197.148.33.

Other host names, for instance serq.net, realtxn.com, asiandmcc.com, kaszoni.org and seal.supply share IP numbers with aggressivecbdregiment.com.

Name Servers

aggressivecbdregiment.com's delegation uses two name servers: ns33.domaincontrol.com and ns34.domaincontrol.com.

aggressivecbdregiment.com uses the same name server setup as other domains, such as adiitworks.com, internetmarketingdirect.com, marypersonalcare.com, fotoswiss.com and onefeed.ai.

aggressivecbdregiment.com at least partially shares name servers with other domains, for example 21fss.com.

Host names with two IPs:

ns33.domaincontrol.com points to 2603:5:21a1::11 and 97.74.106.17

ns34.domaincontrol.com points to 2603:5:22a1::11 and 173.201.74.17

aggressivecbdregiment.com - robtex.com