Security report for chase.com
Chase · Finance · United States
Chase is a leading financial institution providing a wide range of banking and financial services including credit cards, mortgages, auto loans, investing, and business banking. The website serves both personal and business customers with a comprehensive digital platform that supports account management, payments, and financial planning. The brand is well-established with a strong market position as part of JPMorgan Chase & Co., one of the largest banking organizations in the United States. Technically, the website employs modern web technologies such as React and Next.js, ensuring a fast, responsive, and accessible user experience across devices. The site is well-optimized for SEO and includes comprehensive metadata and structured data to enhance search visibility. Security is robust with HTTPS enforcement, secure login forms, and multiple security headers implemented to protect users and data. From a security perspective, the site demonstrates strong best practices including secure forms, no exposed sensitive data, and use of security headers. However, the absence of a publicly visible vulnerability disclosure program and incident response contact details suggests areas for improvement. Privacy compliance is well addressed with clear privacy and cookie policies, including GDPR considerations. Overall, the website is professional, trustworthy, and secure, reflecting the stature of a major financial services provider. The WHOIS data anomaly does not detract from the legitimacy but should be further investigated to ensure domain registration transparency. Strategic recommendations include enhancing vulnerability disclosure visibility, maintaining security certifications, and continuous monitoring of third-party scripts.
Scanned
NIS2 and GDPR posture
- NIS2 outside view
- Not assessed
- GDPR outside view
- Not assessed
Both readouts depend on the site's pages, which could not be loaded in this scan.
Priority findings
1 finding rated critical or high. Fix these first.
SSL/TLS
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
- High
Weak Protocols Supported
Server supports weak protocols: TLSv1.1
What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions
- CWE-327
- OWASP A04:2025
- ASVS V12.1.1
- RFC 8996
- RFC 7568
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: tls_versions TLSv1.2, TLSv1.3
- NIS2 21(2)(h)
- IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
- NIST SC-8(1): NIST SP 800-53 Rev. 5 SC-8(1): Cryptographic Protection
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching chase.com
This scan found 6 issues across 4 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
Daily monitoring
Recommended€25per month
- TLS certificates and expiry
- DNS records
- SPF, DKIM and DMARC
- Security headers
- GDPR and NIS2 posture
- Exposed services
- Third-party trackers
- Security score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.
Full report
€39.90one-time
- The complete analysis as a PDF you can cite
- Email delivery with an unlock code
- Lifetime access to this report
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
How this score is calculated
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
- SSL/TLS
- 82
- Email security
- 85
- DNS health
- 90
- Network security
- 100
- Average
- 89
- After the cap
- 75
Not counted
- Security headers: did not complete in this scan.
- GDPR outside view: did not complete in this scan.
- NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
- OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
- The certificate is not trusted by browsers
- The website is not served over HTTPS
- A database, remote desktop, file-sharing or Telnet service is reachable from the internet
- The page loads a script from a compromised source
- The domain registration has expired
- SPF authorises every server to send mail as the domain
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
- Critical0–25
- High26–49
- Medium50–75
- Low76–100
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- Implement and prominently display a vulnerability disclosure program to encourage responsible reporting of security issues.
- Publish clear incident response contact information to improve transparency and readiness.
- Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
- Maintain and showcase security certifications such as ISO 27001 or SOC 2 to enhance trust.
- Continue enhancing privacy compliance measures and user consent mechanisms in line with evolving regulations.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Chase
- Description
- Chase online; credit cards, mortgages, commercial banking, auto loans, investing & retirement planning, checking and business banking.
- Key services
- Checking accounts, Savings accounts, Credit cards, Mortgages, Auto loans, Investing and retirement planning, Business banking
- Content quality
- excellent
- Branding
- consistent
Technology
- Stack
- React, JavaScript, Webpack, Next.js, CSS, HTML5
- Frameworks
- React, Next.js
- Performance
- fast
- Mobile
- excellent
- Accessibility
- good
- SEO
- good
Security
- Observed score
- 90/100
- Good practices seen
- HTTPS enforced
- Secure login form with password masking
- No exposed sensitive data in HTML
- Use of security headers
Analytics and tracking
- Services
- Boomerang
- Tracking level
- moderate
- Privacy practices
- good
Advertising
- Tracking pixels
- Boomerang
- Marketing tools
- Chase Analytics
- Transparency
- good
Site quality
- Design
- excellent
- User experience
- excellent
- Content relevance
- excellent
- Navigation
- excellent
- Professionalism
- excellent
- Trustworthiness
- high
Key observations
- Website is fully accessible with no blocking or WAF challenge detected.
- Professional and comprehensive financial services website.
- Strong security posture with HTTPS and security headers.
- Clear navigation and extensive service offerings.
- No suspicious or malicious content detected.
- WHOIS data incomplete or unavailable in raw output but does not impact legitimacy.
Technical notes
Notes
Standards and sources
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Earlier scans of this domain
- 83/100Low20 findingsView report
- 83/100 +3Low20 findingsView report
- 80/100Low19 findingsView report
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with chase.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review chase.com.