Back to results

Digital exposure report

chase.com

Good shape, with a few gaps worth closing this quarter.

Scanned: 2026-11-15 19:22 UTC

Partial coverage: the score is based on 95% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.

B
81/100

What to do first

  1. 1.

    Turn on DNS signing for your domain

    Signing helps resolvers detect forged answers about your domain.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short DS chase.com
  2. 2.

    Stop browsers from guessing file types

    This removes one way a file could be treated as something it is not.

    Who can fix it: Your website developer or web host

    How to verify after the fix

    curl -sIL https://chase.com/ | grep -i "X-Content-Type-Options"

A starting point, not a security guarantee.

What this grade means

Tested hostname
chase.com
Website request
GET https://chase.com/ → https://www.chase.com/
Scan time
2026-11-15 19:22:35 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • DKIM — digital signature on email · Not detected (common selectors only)

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Score by category

Email security25/25Spoofing email from this domain is hard.
Encryption & certificate25/25Traffic to the site is encrypted and the certificate is valid.
Browser protections19/30Some browser protections are missing.
DNS infrastructure8/15The domain's infrastructure works, but recommended hardening is missing.

Fix priorities

  1. 1.MediumDNSSEC — signed DNS records · Hardening gap+7
  2. 2.LowX-Content-Type-Options · Hardening gap+4
  3. 3.LowReferrer-Policy · Hardening gap+3
  4. 4.LowCSP — protection from script injection · Hardening gap+3

To verify

Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.

  • DKIM — digital signature on email

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 10/10

An authorized sender list is defined and mail from other servers is rejected.

Valid SPF record with -all. 4 of the 10 allowed DNS lookups.

Source data: DNS TXT chase.com
v=spf1 include:tpo.chase.com exists:%{i}.spf.chase.com exists:%{i}.spf.hc4673-96.iphmx.com exists:%{i}.spf.hc4698-8.iphmx.com -all
$ dig +short TXT chase.com
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.chase.com
v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;
$ dig +short TXT _dmarc.chase.com
Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Not detected (common selectors only) · Severity: OK · Not scored

No DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.

A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.

Source data: DNS TXT <selector>._domainkey.chase.com
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found
google._domainkey: answer
selector1._domainkey: nxdomain
selector2._domainkey: answer
default._domainkey: nxdomain
k1._domainkey: nxdomain
s1._domainkey: answer
s2._domainkey: nxdomain
dkim._domainkey: answer
mail._domainkey: answer
smtp._domainkey: answer
$ dig +short TXT google._domainkey.chase.com
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail exchangers are published for the domain.

4 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

Source data: DNS MX chase.com
20 cluster14.us.messagelabs.com
10 cluster14.us.messagelabs.com
40 cluster14a.us.messagelabs.com
30 cluster14.us.messagelabs.com
$ dig +short MX chase.com
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Passed · Severity: OK · 10/10

The site loads over an encrypted connection.

https://chase.com/ returned HTTP 200 (final URL: https://www.chase.com/). Client-side certificate validation passed.

Source data: HTTPS GET https://chase.com/
HTTP 200
Final URL: https://www.chase.com/
$ curl -sIL https://chase.com/
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Passed · Severity: OK · 7/7

Visitors arriving at an unencrypted address are automatically sent to the secure version.

HTTP 301 → https://www.chase.com/

Source data: HTTP GET http://chase.com/ (redirects not followed)
HTTP 301
Location: https://www.chase.com/
$ curl -sI http://chase.com/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Passed · Severity: OK · 8/8

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. Latest issuance in CT logs: DigiCert, expiring 2027-03-25 (130 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.

Source data: Certificate Transparency logs (certspotter) for chase.com
Live TLS handshake: certificate accepted
CT logs (context only, not scored):
Issuer: DigiCert
Valid from: 2026-09-08
Valid until: 2027-03-25
Names: chase.com, www-ndc.chase.com, www.chase.com
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect chase.com:443 -servername chase.com 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Passed · Severity: OK · 7/8

Browsers are told to always use an encrypted connection to the site.

max-age=31536000 (365 days), no includeSubDomains. ≥ 180 days recommended.

Source data: Response headers from https://www.chase.com/
Strict-Transport-Security: max-age=31536000
$ curl -sIL https://chase.com/ | grep -i "Strict-Transport-Security"
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Needs attention · Severity: Low · Hardening gap · 5/8

A script policy exists, but it's permissive and offers only partial protection.

script-src includes: no script-src/default-src — weakens XSS protection.

Source data: Response headers from https://www.chase.com/
Content-Security-Policy: frame-ancestors 'none'
$ curl -sIL https://chase.com/ | grep -i "Content-Security-Policy"
Fix recommendation (effort: Complex)
  1. First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
  2. Collect violations for a week or two and tune the policy to your legitimate sources.
  3. Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/*
  Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'

Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.

Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Passed · Severity: OK · 5/5

The site can't be embedded by foreign sites.

X-Frame-Options: SAMEORIGIN frame-ancestors 'none'

Source data: Response headers from https://www.chase.com/
X-Frame-Options: SAMEORIGIN
CSP frame-ancestors: 'none'
$ curl -sIL https://chase.com/ | grep -i "X-Frame-Options"
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Failed · Severity: Low · Hardening gap · 0/4

The browser may interpret files as code unintentionally.

Missing X-Content-Type-Options: nosniff header (MIME sniffing).

Source data: Response headers from https://www.chase.com/
X-Content-Type-Options: (missing)
$ curl -sIL https://chase.com/ | grep -i "X-Content-Type-Options"
Fix recommendation (effort: Easy)
  1. Add X-Content-Type-Options: nosniff to every response.
/*
  X-Content-Type-Options: nosniff

Safety: This change is made in your server/CDN settings. Test on staging before production.

Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Failed · Severity: Low · Hardening gap · 0/3

Internal URLs (including parameters) may leak to external sites.

Referrer-Policy is missing; the browser will use its default.

Source data: Response headers from https://www.chase.com/
Referrer-Policy: (missing)
$ curl -sIL https://chase.com/ | grep -i "Referrer-Policy"
Fix recommendation (effort: Easy)
  1. Set Referrer-Policy: strict-origin-when-cross-origin.
/*
  Referrer-Policy: strict-origin-when-cross-origin

Safety: This change is made in your server/CDN settings. Test on staging before production.

Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Passed · Severity: OK · 2/2

The site restricts access to sensitive browser features.

Permissions-Policy: ch-ua-full-version-list=("https://*.chase.com"),ch-ua-platform-version=("https://*.chase.com"),ch-ua-arch=("https://*.chase.com"),ch-ua-model=("https://*.chase.

Source data: Response headers from https://www.chase.com/
Permissions-Policy: ch-ua-full-version-list=("https://*.chase.com"),ch-ua-platform-version=("https://*.chase.com"),ch-ua-arch=("https://*.chase.com"),ch-ua-model=("https://*.chase.com"),ch-ua-bitness=("https://*.chase.com"),ch-ua-wow64=("https://*.chase.com")
$ curl -sIL https://chase.com/ | grep -i "Permissions-Policy"
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Software version disclosure

Passed · Severity: OK · unscored

The server doesn't disclose software versions.

No version numbers found in the Server / X-Powered-By headers.

Source data: Response headers from https://www.chase.com/
server: cloudflare
x-powered-by: (missing)
$ curl -sIL https://chase.com/ | grep -iE "^(server|x-powered-by)"
Documentation: OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.

No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS chase.com: NODATA
$ dig +short DS chase.com
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec chase.com SOA
delv chase.com

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.

Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Passed · Severity: OK · 5/5

Only authorized certificate authorities can issue certificates for the domain.

CAA records: 0 issue "digicert.com" | 0 issue "entrust.net"

Source data: DNS CAA chase.com
0 issue "digicert.com"
0 issue "entrust.net"
$ dig +short CAA chase.com
Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

6 NS servers.

Source data: DNS NS chase.com
ns06.jpmorganchase.com
ns0140.secondary.cloudflare.com
ns0119.secondary.cloudflare.com
ns05.jpmorganchase.com
ns2.jpmorganchase.com
ns1.jpmorganchase.com
$ dig +short NS chase.com
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

  • Google & Yahoo sender rules1 unverified
  • PCI DSS v4.01 observed gaps
  • NIS2 / vendor due diligence1 observed gaps
  • SOC 2 / ISO 27001 baseline2 observed gaps

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Public DNS records

Achase.com146.143.141.57 | 146.143.83.57 | 146.143.13.57
AAAAchase.com—
MXchase.com20 cluster14.us.messagelabs.com | 10 cluster14.us.messagelabs.com | 40 cluster14a.us.messagelabs.com | 30 cluster14.us.messagelabs.com
NSchase.comns06.jpmorganchase.com | ns0140.secondary.cloudflare.com | ns0119.secondary.cloudflare.com | ns05.jpmorganchase.com | ns2.jpmorganchase.com | ns1.jpmorganchase.com
TXTchase.comv=spf1 include:tpo.chase.com exists:%{i}.spf.chase.com exists:%{i}.spf.hc4673-96.iphmx.com exists:%{i}.spf.hc4698-8.iphmx.com -all | wiz-domain-verification=ccd3ec907fff510311f6a14b2a659fcb83adea2818bb6e78503239d2877e8657? | docusign=b04ddbec-21ac-4d6b-bb8b-3f1a3bca079f | smartsheet-site-validation=JdBS3Kn_332V6dI9U0iq0TV3RZZXTUhL | docusign=500adee6-4cca-451d-bcd8-2813346419c8 | google-site-verification=w00TwyVREI5RpqAT9hqSLZVvZcZi46578G57D1aMGeE | sinch-domain-verification=6848bb42-da6f-49cf-8974-920af9cf1806 | google-site-verification=PfSAyrffyVUKXLc1Ew8C2IFPWkjufFSsbboFz_24Qt4 | google-site-verification=iZwZzo1YPl0G29U136Suzn4c1VptcA_LkvvdWOYC6B0 | wiz-domain-verification=a0d8d067bcb1cdd44255d0633a31df3ba13c82e30f27c080519b0b85ba734d32 | pendo-domain-verification=1f6e5677-d405-438e-88ba-141766793ce8 | _m47rp0d9u3ci4ycif1echp310q0yy09 | wiz-domain-verification=66aa74155d5e84d10ed4b5a786a66f94063cff3b4c7e11d09fb46f027736dbf0 | airtable-verification=1d59ed5062280d21aeef0c14aaf4f950 | atlassian-domain-verification\\u003dpD6ozLCGDinP/R+vd5R9hpoPCSOmTFTHfWPK633PXEtELa5KlVDw4w1Pnn02aTdC | wiz-domain-verification=68c6d9fa0c4bdd60150d3df50635cd0fcf4af6af079771d90239d10add2c2967 | atlassian-domain-verification=wUjrfh2T73RznZOKmEZfc0mRF92bjC7JyjSgRXg9Yt2e9ZMRZwafUO6GPJaecYOh | atlassian-domain-verification=Ua2Fovb97Ak39kxh4koulfhVlpieV1PLhaMkdZpzINDMQGlcvLV+ORgL2QmOryw+ | atlassian-domain-verification=PZApk1vJjd7scChzBMQy2d4NEwk4Bt26obCVACc7vWiOBVCOxTOV4/EB9LMexMnl | DirectFedAuthUrl=https://idauatg2.jpmorganchase.com/adfs/ls/ | onetrust-domain-verification=ccee45576c1e4fbfaa4014725a73344f | 00D4J000000FQcn=1TBJ7000000blJn
TXT_dmarc.chase.comv=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;
CAAchase.com0 issue "digicert.com" | 0 issue "entrust.net"
DSchase.com—
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain