Verifying against the live site and live WHOIS/DNS…
Common questions
Is jpmorganchase.com legit or a scam?
jpmorganchase.com was registered Sep 12, 2000 (26 years old), per public registration records. AboutUs doesn't label sites "legit" or "a scam": this page lists the dated registration, DNS, HTTPS, mail-authentication and safety checks we could verify, each with its source, so you can decide for yourself.
Who owns jpmorganchase.com?
Nobody has completed AboutUs's owner verification for jpmorganchase.com. That's true of most sites here — it isn't itself a warning sign.
When was jpmorganchase.com registered?
jpmorganchase.com's registration dates to Sep 12, 2000 (26 years old), per public registration records. MarkMonitor Inc. is the registrar on record today.
Correct a description, link or other detail. Submissions are reviewed before publication.
Lifeline · jpmorganchase.com over time
Checked in the last 30 daysOlder, dated recordFrom registration records
Registered 26 years ago · on AboutUs since 2013 · 1 registrar change since May 21, 2007 · no registrant change on record since 2007 · last checked Nov 22, 2026.
Registration
RegisteredSep 12, 2000jpmorganchase.com was registered on Sep 12, 2000.Source: RDAP, fetched Oct 25, 2026
AboutUs record
AboutUs wiki pageNov 13, 2013An AboutUs wiki page described jpmorganchase.com from Nov 13, 2013 to Nov 13, 2013 (1 edit).Source: AboutUs wiki archive, 2006–2023Current AboutUs recordJun 25, 2026 – Nov 15, 2026 (latest)Authority and Safety last refreshed Nov 15, 2026.Source: AboutUs checks
Registrar
Markmonitor.comMarkmonitor.comMay 21, 2007 – Nov 8, 2013Registrar Markmonitor.com in the WHOIS and RDAP records held for jpmorganchase.com, from May 21, 2007 to Nov 8, 2013.Source: WHOIS / RDAP archive (who.is)MarkMonitor, Inc.
Registrant
Registrant recordsMay 21, 2007 – Jun 17, 2026Registration records for jpmorganchase.com are held from May 21, 2007 to Jun 17, 2026 (763 records). None shows a change of registrant. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
No registrant changes recorded, 2007–2026
Zone file
Nameservers: jpmorganchase.comNameservers: jpmorganchase.comMay 21, 2007 – Oct 17, 2013Registration records listed jpmorganchase.com nameservers (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) for jpmorganchase.com from May 21, 2007 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Certificate
DigiCert IncDigiCert IncJan 13, 2026 – Nov 22, 2026 (latest)DigiCert Inc issued 207 certificates for jpmorganchase.com from Jan 13, 2026, the latest valid until Jun 4, 2027. Seen in use on Nov 4, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Nov 4, 2026
20102020Jan ’26Jul ’26← last 12 months, drawn wider
Every dated fact on this lifeline (17)
Sep 12, 2000Registration: jpmorganchase.com was registered on Sep 12, 2000.Source: RDAP, fetched Oct 25, 2026
May 21, 2007 – Nov 8, 2013Registrar: Registrar Markmonitor.com in the WHOIS and RDAP records held for jpmorganchase.com, from May 21, 2007 to Nov 8, 2013.Source: WHOIS / RDAP archive (who.is)
May 21, 2007 – Jun 17, 2026Registrant: Registration records for jpmorganchase.com are held from May 21, 2007 to Jun 17, 2026 (763 records). None shows a change of registrant. Privacy-service and redaction changes, renames of the same organization and new contacts at it are not counted.Source: WHOIS / RDAP archive (who.is); counted by registrant name and organization only
May 21, 2007 – Oct 17, 2013Zone file: Registration records listed jpmorganchase.com nameservers (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) for jpmorganchase.com from May 21, 2007 to Oct 17, 2013. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Oct 18, 2013 – Apr 1, 2016Zone file: jpmorganchase.com (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) were the nameservers listed for jpmorganchase.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).
MarkMonitor, Inc.
Nov 14, 2013 – Nov 21, 2026 (latest)
Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Nov 14, 2013 and most recently on Nov 21, 2026.
Source: RDAP, fetched Oct 25, 2026
Nameservers: jpmorganchase.comOct 18, 2013 – Apr 1, 2016jpmorganchase.com (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) were the nameservers listed for jpmorganchase.com at every ICANN zone-file snapshot AboutUs holds from Oct 18, 2013 to Apr 1, 2016 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nameservers: Oracle DynJun 29, 2016 – Apr 2, 2018Registration records listed Oracle Dyn nameservers (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) for jpmorganchase.com from Jun 29, 2016 to Apr 2, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to Oracle DynJun 29, 2016jpmorganchase.com's nameservers moved from jpmorganchase.com to Oracle Dyn at some point between Apr 1, 2016 and Jun 29, 2016. Last seen at jpmorganchase.com: Apr 1, 2016 (ICANN zone-file snapshot). First seen at Oracle Dyn: Jun 29, 2016 (registration record). AboutUs holds no nameserver records for the 3 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → registration record)
Nameservers: Oracle DynApr 3, 2018Oracle Dyn (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) were the nameservers listed for jpmorganchase.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Nameservers: Oracle DynApr 4, 2018 – May 24, 2021Registration records listed Oracle Dyn nameservers (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) for jpmorganchase.com from Apr 4, 2018 to May 24, 2021. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Nameservers: CloudflareNameservers: CloudflareJun 10, 2021 – Jun 17, 2026Registration records listed Cloudflare nameservers (ns0087.secondary.cloudflare.com, ns0134.secondary.cloudflare.com, ns05.jpmorganchase.com…) for jpmorganchase.com from Jun 10, 2021 to Jun 17, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
DNS moved to CloudflareJun 10, 2021jpmorganchase.com's nameservers moved from Oracle Dyn to Cloudflare between May 24, 2021 and Jun 10, 2021. Last seen at Oracle Dyn: May 24, 2021 (registration record). First seen at Cloudflare: Jun 10, 2021 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Seen in the .com zone fileSep 8, 2026 – Nov 22, 2026 (latest)First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 22, 2026. Nameservers on Nov 22, 2026: ns0087.secondary.cloudflare.com, ns0134.secondary.cloudflare.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com….Source: ICANN CZDS zone file, snapshot Nov 22, 2026
Let's Encrypt
Aug 5, 2026 – Nov 22, 2026
Let's Encrypt issued 8 certificates for jpmorganchase.com from Aug 5, 2026, the latest valid until Jan 6, 2027.
Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Nov 13, 2013AboutUs record: An AboutUs wiki page described jpmorganchase.com from Nov 13, 2013 to Nov 13, 2013 (1 edit).Source: AboutUs wiki archive, 2006–2023
Nov 14, 2013 – Nov 21, 2026Registrar: Registrar MarkMonitor, Inc. (IANA 292) in the registration data recorded, first on Nov 14, 2013 and most recently on Nov 21, 2026.Source: RDAP, fetched Oct 25, 2026
Jun 29, 2016 – Apr 2, 2018Zone file: Registration records listed Oracle Dyn nameservers (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) for jpmorganchase.com from Jun 29, 2016 to Apr 2, 2018. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 29, 2016Zone file: jpmorganchase.com's nameservers moved from jpmorganchase.com to Oracle Dyn at some point between Apr 1, 2016 and Jun 29, 2016. Last seen at jpmorganchase.com: Apr 1, 2016 (ICANN zone-file snapshot). First seen at Oracle Dyn: Jun 29, 2016 (registration record). AboutUs holds no nameserver records for the 3 months in between, so the date of the move is not known more closely.Source: Derived from the nameserver records on this lifeline (ICANN zone-file snapshot → registration record)
Apr 3, 2018Zone file: Oracle Dyn (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) were the nameservers listed for jpmorganchase.com at every ICANN zone-file snapshot AboutUs holds from Apr 3, 2018 to Apr 3, 2018 (snapshots exist for only part of 2013–2018).Source: ICANN zone-file snapshots, 2013–2018 (legacy archive)
Apr 4, 2018 – May 24, 2021Zone file: Registration records listed Oracle Dyn nameservers (ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com…) for jpmorganchase.com from Apr 4, 2018 to May 24, 2021. Days a zone file covers are shown from the zone file instead.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 10, 2021 – Jun 17, 2026Zone file: Registration records listed Cloudflare nameservers (ns0087.secondary.cloudflare.com, ns0134.secondary.cloudflare.com, ns05.jpmorganchase.com…) for jpmorganchase.com from Jun 10, 2021 to Jun 17, 2026.Source: From registration records (WHOIS / RDAP archive, who.is)
Jun 10, 2021Zone file: jpmorganchase.com's nameservers moved from Oracle Dyn to Cloudflare between May 24, 2021 and Jun 10, 2021. Last seen at Oracle Dyn: May 24, 2021 (registration record). First seen at Cloudflare: Jun 10, 2021 (registration record).Source: Derived from the nameserver records on this lifeline (registration record → registration record)
Jan 13, 2026 – Nov 22, 2026Certificate: DigiCert Inc issued 207 certificates for jpmorganchase.com from Jan 13, 2026, the latest valid until Jun 4, 2027. Seen in use on Nov 4, 2026.Source: Certificate Transparency logs (AboutUs's own certificate-log reader); TLS check, Nov 4, 2026
Jun 25, 2026 – Nov 15, 2026AboutUs record: Authority and Safety last refreshed Nov 15, 2026.Source: AboutUs checks
Aug 5, 2026 – Nov 22, 2026Certificate: Let's Encrypt issued 8 certificates for jpmorganchase.com from Aug 5, 2026, the latest valid until Jan 6, 2027.Source: Certificate Transparency logs (AboutUs's own certificate-log reader)
Sep 8, 2026 – Nov 22, 2026Zone file: First seen in the .com zone file records AboutUs holds on Sep 8, 2026; latest sighting Nov 22, 2026. Nameservers on Nov 22, 2026: ns0087.secondary.cloudflare.com, ns0134.secondary.cloudflare.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com….Source: ICANN CZDS zone file, snapshot Nov 22, 2026
Registered 2000 · site is live · HTTPS valid
JPMorgan Chase (NYSE: JPM) provides investment banking, consumer and commercial banking, financial transaction processing, asset management, and private equity services globally. The firm serves consumers, small businesses, corporations, and institutional clients across more than 60 countries.
Authority 83/100— ahead of 83% of the August 2026 scored sampleClear
Why this authority score
83 is a percentile: higher than 83% of sites we score.
How it's calculated
Prominence (Tranco rank #7,445)+9
Verified continuity: 26.2 years (RDAP registration)+11
Security & email hygiene+4
Calibration adjustment (published map)+18
Model score: 42/99 — what these reason lines add up to.
Published Authority (percentile): 83/100 — this site's rank against the August 2026 scored sample. Public Authority is capped at 99.
Safety evidence
Retained threat-feed result (recorded about 7 days ago); name-similarity check available (recorded about 7 days ago); 3/3 transport and email checks available (oldest recorded about 7 days ago). This is evidence coverage, not a probability that a website is safe.
Site history
Dated record — historical facts always carry their date.