🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`chase-updates.com`

DNSSEC	⚠️ Not signed
NS	`ns1.jpmorganchase.com` ⭐
		A	146.143.67.130^{🇺🇸 AS3486146.143.64.0/18}
			PTR	`ns1.jpmorganchase.com`
NS	`ns0037.secondary.cloudflare.com` ⚠️ Not in parent delegation
		A	2606:4700:51::a29f:2026^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns0037.secondary.cloudflare.com`
		A	162.159.32.38^{Cloudflare162.159.32.0/23 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns0037.secondary.cloudflare.com`
NS	`ns0246.secondary.cloudflare.com` ⚠️ Not in parent delegation
		A	2606:4700:59::a29f:2179^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns0246.secondary.cloudflare.com`
		A	162.159.33.121^{Cloudflare162.159.32.0/23 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns0246.secondary.cloudflare.com`
NS	`ns05.jpmorganchase.com`
		A	146.143.195.130^{🇺🇸 AS3486146.143.192.0/18}
			PTR	`ns05.jpmorganchase.com`
NS	`ns06.jpmorganchase.com`
		A	146.143.131.130^{🇺🇸 AS3486146.143.128.0/18}
			PTR	`ns06.jpmorganchase.com`
NS	`ns2.jpmorganchase.com`
		A	146.143.3.130^{🇺🇸 AS3486146.143.0.0/18}
			PTR	`ns2.jpmorganchase.com`
TXT	`v=spf1 -all`
SOA	`ns1.jpmorganchase.com`hostmaster@jpmchase.com serial=656929418

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

Same first word

chase-updates.eu

chase-updates.com

Previous names

Next names

DNS History

18 records (6 active, 12 former)

○NSdns026.c.register.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○NSdns099.a.register.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○NSdns139.b.register.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○NSdns177.d.register.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

●NSns0037.secondary.cloudflare.com2026-08-12 → 2026-08-17 · 3 obs

○ 2016-02-12 12:57:42
● 2026-08-12 03:25:04
● 2026-08-17 20:05:04

●NSns0246.secondary.cloudflare.com2026-08-12 → 2026-08-17 · 3 obs

○ 2016-02-12 12:57:42
● 2026-08-12 03:25:04
● 2026-08-17 20:05:04

●NSns05.jpmorganchase.com2016-02-12 → 2026-08-17 · 3 obs

○ 2015-11-12 02:59:10
● 2016-02-12 12:57:42
● 2026-08-17 20:05:04

●NSns06.jpmorganchase.com2016-02-12 → 2026-08-17 · 3 obs

○ 2015-11-12 02:59:10
● 2016-02-12 12:57:42
● 2026-08-17 20:05:04

●NSns1.jpmorganchase.com2016-02-12 → 2026-08-17 · 3 obs

○ 2015-11-12 02:59:10
● 2016-02-12 12:57:42
● 2026-08-17 20:05:04

●NSns2.jpmorganchase.com2016-02-12 → 2026-08-17 · 3 obs

○ 2015-11-12 02:59:10
● 2016-02-12 12:57:42
● 2026-08-17 20:05:04

○MXalt1.aspmx.l.google.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○MXalt2.aspmx.l.google.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○MXaspmx.l.google.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○MXaspmx2.googlemail.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○MXaspmx3.googlemail.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○MXaspmx4.googlemail.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○MXaspmx5.googlemail.com2015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

○A199.34.228.722015-06-30 → 2015-06-30 · 3 obs

● 2015-06-30 22:34:16
○ 2015-11-12 02:59:10
○ 2026-08-17 20:05:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net...	-
chase-updates.com	ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com	4 records

✅ Authoritative Response

Server:146.143.67.130

NS records: ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for chase-updates.com (unsigned zone)

⏱️ Timing

Total: 358ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	6	`ns06.jpmorganchase.com, ns0246.secondary.cloudflare.com...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.jpmorganchase.com hostmaster.jpmchas`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com...)

Analysis

Name Servers

chase-updates.com has 6 name servers — ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com and 3 others.

At least some of chase-updates.com's name servers are shared with other domains, for example jpmorganrussiaonline.com.ru, jems-jpmorgan.net, jpmorganevents.net and two more.

These name servers tend to co-occur with ns2.jpmorganchase.com, ns0037.secondary.cloudflare.com, ns0246.secondary.cloudflare.com and 4 other name servers in the same DNS delegations.

Hosts with two IP numbers each:

ns0037.secondary.cloudflare.com resolves to 162.159.32.38 and 2606:4700:51::a29f:2026.

ns0246.secondary.cloudflare.com resolves to 162.159.33.121 and 2606:4700:59::a29f:2179.

Hosts that resolve to one IP address:

ns05.jpmorganchase.com resolves to 146.143.195.130.

ns06.jpmorganchase.com resolves to 146.143.131.130.

ns1.jpmorganchase.com resolves to 146.143.67.130.

ns2.jpmorganchase.com resolves to 146.143.3.130.