contentchase.com - dns.ninja

`contentchase.com`

DNSSEC	⚠️ Not signed
A	2a02:4780:b:1342:0:bf0:3157:10^{🇺🇸 IIHOS0012a02:4780:b::/48 HOSTINGER US}
A	50.62.221.221^{🇺🇸 AS39810150.62.220.0/22 GCN Allocation}
NS	`ns1.dns-parking.com` ⭐
		A	2400:cb00:2049:1::a29f:18c9^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.201^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dns-parking.com`
NS	`ns2.dns-parking.com`
		A	2400:cb00:2049:1::a29f:192a^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.25.42^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dns-parking.com`
MX	`mx1.hostinger.com` ⭐
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx2.hostinger.com`⁽¹⁰⁾
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 include:_spf.mail.hostinger.com ~all`
SOA	`ns1.dns-parking.com`dns@hostinger.com 2026-07-30 #1

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

Previously MX for

contentchase.com

Same first word

contentchase.com

DNS History

25 records (6 active, 19 former)

○NS1.namedc.com2015-06-21 → 2017-09-01 · 5 obs

○ 2008-03-07 23:24:10
● 2015-06-21 20:36:26
● 2017-09-01 21:02:02
○ 2026-02-16 06:52:34
○ 2026-08-05 23:02:24

○NS2.namedc.com2015-06-21 → 2017-09-01 · 5 obs

○ 2008-03-07 23:24:10
● 2015-06-21 20:36:26
● 2017-09-01 21:02:02
○ 2026-02-16 06:52:34
○ 2026-08-05 23:02:24

●NSns1.dns-parking.com2026-02-16 → 2026-08-05 · 3 obs

○ 2017-09-01 21:02:02
● 2026-02-16 06:52:34
● 2026-08-05 23:02:24

●NSns2.dns-parking.com2026-02-16 → 2026-08-05 · 3 obs

○ 2017-09-01 21:02:02
● 2026-02-16 06:52:34
● 2026-08-05 23:02:24

○NSns8.san.yahoo.com2008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○NSns9.san.yahoo.com2008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○NSyns1.yahoo.com2008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○NSyns2.yahoo.com2008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○MXcontentchase.com2015-10-28 → 2017-09-01 · 5 obs

○ 2015-06-21 20:36:26
● 2015-10-28 18:03:48
● 2017-09-01 21:02:02
○ 2026-02-16 06:52:34
○ 2026-08-05 23:02:24

○MXmail.contentchase.com2015-06-21 → 2015-06-21 · 4 obs

○ 2008-03-07 23:24:10
● 2015-06-21 20:36:26
○ 2015-10-28 18:03:48
○ 2026-08-05 23:02:24

○MXmx1.biz.mail.yahoo.com2008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

●MXmx1.hostinger.com2026-02-16 → 2026-08-05 · 3 obs

○ 2017-09-01 21:02:02
● 2026-02-16 06:52:34
● 2026-08-05 23:02:24

●MXmx2.hostinger.com2026-02-16 → 2026-08-05 · 3 obs

○ 2017-09-01 21:02:02
● 2026-02-16 06:52:34
● 2026-08-05 23:02:24

○MXmx5.biz.mail.yahoo.com2008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○A192.82.250.1692015-06-21 → 2015-06-21 · 4 obs

○ 2008-03-07 23:24:10
● 2015-06-21 20:36:26
○ 2015-10-28 18:03:48
○ 2026-08-05 23:02:24

○A216.39.58.1932008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○A216.39.58.1942008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○A216.39.58.1952008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○A216.39.58.1962008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○A216.39.58.1972008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

○A216.39.58.1982008-03-07 → 2008-03-07 · 3 obs

● 2008-03-07 23:24:10
○ 2015-06-21 20:36:26
○ 2026-08-05 23:02:24

●A2a02:4780:b:1342:0:bf0:3157:102026-02-16 → 2026-08-05 · 3 obs

○ 2017-09-01 21:02:02
● 2026-02-16 06:52:34
● 2026-08-05 23:02:24

●A50.62.221.2212026-02-16 → 2026-08-05 · 3 obs

○ 2017-09-01 21:02:02
● 2026-02-16 06:52:34
● 2026-08-05 23:02:24

○A64.37.52.22015-10-28 → 2016-12-03 · 5 obs

○ 2015-06-21 20:36:26
● 2015-10-28 18:03:48
● 2016-12-03 08:29:34
○ 2017-09-01 21:02:02
○ 2026-08-05 23:02:24

○A67.23.226.1892017-09-01 → 2017-09-01 · 4 obs

○ 2016-12-03 08:29:34
● 2017-09-01 21:02:02
○ 2026-02-16 06:52:34
○ 2026-08-05 23:02:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net...	-
contentchase.com	ns1.dns-parking.com, ns2.dns-parking.com	4 records

✅ Authoritative Response

Server:162.159.24.201

NS records: ns1.dns-parking.com, ns2.dns-parking.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for contentchase.com (unsigned zone)

⏱️ Timing

Total: 345ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`50.62.221.221`
AAAA	1	`2a02:4780:b:1342:0:bf0:3157:10`
NS	2	`ns2.dns-parking.com, ns1.dns-parking.com`
MX	2	`mx1.hostinger.com (pri: 5), mx2.hostinger.com (pri: 10)`
TXT	1	`v=spf1 include:_spf.mail.hostinger.com ~`
SOA	1	`ns1.dns-parking.com dns.hostinger.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.dns-parking.com, ns1.dns-parking.com, ns2.dns-parking.com...)

Analysis

IP Addresses

contentchase.com points to the IP addresses 50.62.221.221 and 2a02:4780:b:1342:0:bf0:3157:10

avatarit.net, asi-industrial.com, parkcitiestactical.com and two other host names share IP numbers with contentchase.com.

Name Servers

The NS records for contentchase.com delegate to ns1.dns-parking.com and ns2.dns-parking.com.

contentchase.com uses the same name servers as several other domains — among them outletlite.com, armcombo.xyz, mybrandplease.com and two more.

ns1.dns-parking.com resolves to 162.159.24.201 and 2400:cb00:2049:1::a29f:18c9. Likewise, ns2.dns-parking.com resolves to 162.159.25.42 and 2400:cb00:2049:1::a29f:192a — two IP addresses apiece.

Mail Servers

Mail for contentchase.com is handled by two mail servers — mx1.hostinger.com and mx2.hostinger.com.

contentchase.com uses an identical mail server configuration to several other domains — among them rc-international.info, alicefoxx.com, adtechinfo.com and two more.

At least a portion of contentchase.com's mail servers are shared with other domains, among them maxbitzer.com and primflux.com.

mx1.hostinger.com has IP addresses 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f; mx2.hostinger.com has the same IP addresses: 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f.

mx1.hostinger.com and mx2.hostinger.com each have 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

mx1.hostinger.com and mx2.hostinger.com each have 172.65.182.103 IP addresses.