`chasing-history.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	`ns35.domaincontrol.com` ⭐
		A	2603:5:21b1::12^{🇺🇸 GODADDY-DNS2603:5:21b0::/44}
			PTR	`ns35.domaincontrol.com`
		A	97.74.107.18^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns35.domaincontrol.com`
NS	`ns36.domaincontrol.com`
		A	2603:5:22b1::12^{🇺🇸 GODADDY-DNS2603:5:22b0::/44}
			PTR	`ns36.domaincontrol.com`
		A	173.201.75.18^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns36.domaincontrol.com`
SOA	`ns35.domaincontrol.com`dns@jomax.net 2023-09-19 #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

chasing-history.com

DNS History

9 records (4 active, 5 former)

●NSns35.domaincontrol.com2026-03-05 → 2026-03-24 · 3 obs

○ 2015-10-20 19:35:26
● 2026-03-05 20:33:42
● 2026-03-24 06:39:04

●NSns36.domaincontrol.com2026-03-05 → 2026-03-24 · 3 obs

○ 2015-10-20 19:35:26
● 2026-03-05 20:33:42
● 2026-03-24 06:39:04

○NSns51.domaincontrol.com2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 09:38:34
○ 2015-10-20 19:35:26
○ 2026-03-24 06:39:04

○NSns52.domaincontrol.com2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 09:38:34
○ 2015-10-20 19:35:26
○ 2026-03-24 06:39:04

○MXmailstore1.secureserver.net2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 09:38:34
○ 2015-10-20 19:35:26
○ 2026-03-24 06:39:04

○MXsmtp.secureserver.net2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 09:38:34
○ 2015-10-20 19:35:26
○ 2026-03-24 06:39:04

●A15.197.148.332026-03-05 → 2026-03-24 · 3 obs

○ 2015-10-20 19:35:26
● 2026-03-05 20:33:42
● 2026-03-24 06:39:04

●A3.33.130.1902026-03-05 → 2026-03-24 · 3 obs

○ 2015-10-20 19:35:26
● 2026-03-05 20:33:42
● 2026-03-24 06:39:04

○A68.178.232.1002008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 09:38:34
○ 2015-10-20 19:35:26
○ 2026-03-24 06:39:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
chasing-history.com	ns35.domaincontrol.com, ns36.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.107.18

NS records: ns35.domaincontrol.com, ns36.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for chasing-history.com (unsigned zone)

⏱️ Timing

Total: 115ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)

Analysis

IP Addresses

The entity chasing-history.com points to two IP numbers: 3.33.130.190 and 15.197.148.33.

For instance, other host names vitalsoft.co.uk, emcattle.com, (0x736578)onorte.com, dadsofbrooklyn.com and conversio.io share IP numbers with chasing-history.com.

Name Servers

chasing-history.com is delegated to two name servers: ns35.domaincontrol.com and ns36.domaincontrol.com.

chasing-history.com uses the same name server setup as other domains such as bakballs.com, thesezar.com, footballthecardgame.com, chargeonus.com and spois.com.

chasing-history.com shares name servers with other domains at least partially, for example gbnite.com.

Host names with two IP numbers:

ns35.domaincontrol.com points to 2603:5:21b1::12 and 97.74.107.18; ns36.domaincontrol.com points to 2603:5:22b1::12 and 173.201.75.18.

chasing-history.com - robtex.com