`capture-collective.com`

DNSSEC	⚠️ Not signed
NS	`dns1.parastorage.com` ⚠️ Not in zone NS records
		A	18.235.106.15^{🇺🇸 Amazon18.232.0.0/14 EC2 IAD prefix}
			PTR	`ec2-18-235-106-15.compute-1.amazonaws.com`
		A	44.199.133.20^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-199-133-20.compute-1.amazonaws.com`
NS	`dns2.parastorage.com` ⚠️ Not in zone NS records
		A	35.166.161.189^{🇺🇸 Amazon35.160.0.0/13 EC2 PDX prefix}
			PTR	`ec2-35-166-161-189.us-west-2.compute.amazonaws.com`
		A	44.224.60.7^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
			PTR	`ec2-44-224-60-7.us-west-2.compute.amazonaws.com`

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

Same first word

capture-collective.com

DNS History

15 records (2 active, 13 former)

●NSdns1.parastorage.com2026-03-19 → 2026-03-28 · 3 obs

○ 2026-02-15 15:27:52
● 2026-03-19 09:47:12
● 2026-03-28 10:38:52

●NSdns2.parastorage.com2026-03-19 → 2026-03-28 · 3 obs

○ 2026-02-15 15:27:52
● 2026-03-19 09:47:12
● 2026-03-28 10:38:52

○NSns1.nameserver.center2020-02-03 → 2020-02-03 · 3 obs

● 2020-02-03 09:56:44
○ 2026-02-15 15:27:52
○ 2026-03-28 10:38:52

○NSns12.wixdns.net2026-02-15 → 2026-02-15 · 4 obs

○ 2020-02-03 09:56:44
● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○NSns13.wixdns.net2026-02-15 → 2026-02-15 · 4 obs

○ 2020-02-03 09:56:44
● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○NSns2.nameserver.center2020-02-03 → 2020-02-03 · 3 obs

● 2020-02-03 09:56:44
○ 2026-02-15 15:27:52
○ 2026-03-28 10:38:52

○MXalt1.aspmx.l.google.com2026-02-15 → 2026-02-15 · 3 obs

● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○MXalt2.aspmx.l.google.com2026-02-15 → 2026-02-15 · 3 obs

● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○MXalt3.aspmx.l.google.com2026-02-15 → 2026-02-15 · 3 obs

● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○MXalt4.aspmx.l.google.com2026-02-15 → 2026-02-15 · 3 obs

● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○MXaspmx.l.google.com2026-02-15 → 2026-02-15 · 3 obs

● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○A185.230.63.1072026-02-15 → 2026-02-15 · 4 obs

○ 2020-02-03 09:56:44
● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○A185.230.63.1712026-02-15 → 2026-02-15 · 4 obs

○ 2020-02-03 09:56:44
● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○A185.230.63.1862026-02-15 → 2026-02-15 · 4 obs

○ 2020-02-03 09:56:44
● 2026-02-15 15:27:52
○ 2026-03-19 09:47:12
○ 2026-03-28 10:38:52

○A78.46.40.202020-02-03 → 2020-02-03 · 3 obs

● 2020-02-03 09:56:44
○ 2026-02-15 15:27:52
○ 2026-03-28 10:38:52

🔍 DNS Trace

Analysis

Name Servers

capture-collective.com's delegation uses two name servers: dns1.parastorage.com and dns2.parastorage.com.

capture-collective.com uses the same name server setup as other domains, such as simonbachelet.com, cadnv.com, you-can-learn.com, amothersjoy.com and pecasbavoso.com.

Host names with two IPs:

dns1.parastorage.com points to 18.235.106.15 and 44.199.133.20

dns2.parastorage.com points to 35.166.161.189 and 44.224.60.7

capture-collective.com - robtex.com