chase.com
HTTPS & TLS
100/100A+- HTTPS certificateDigiCert Inc10/10
HTTPS with a valid certificate from DigiCert Inc.
- Certificate expiry844/4
The certificate is valid for another 84 days.
- TLS versionTLS 1.34/4
Negotiates TLS 1.3, the current protocol: faster handshakes, forward secrecy always.
- Old protocols3/3
Refuses the retired TLS 1.0 and 1.1.
- Key strengthRSA 20482/2
A strong key: RSA 2048.
- HTTP → HTTPS3013/3
http:// redirects straight to https://.
- HSTS1 year4/4
HSTS tells browsers to use HTTPS only, for 1 year.
- HTTP/2 and HTTP/3HTTP/22/2
HTTP/2.
DNS
79/100B- DNSSEC0/3
Not signed with DNSSEC: a forged DNS answer for the domain cannot be told from the real one.
- Name servers64/4
6 name servers for the domain.
- Name servers answer6/65/5
Every name server answers for the domain, with the same version of the zone.
- CAA recordsentrust.net, digicert.com2/2
CAA records name the authorities allowed to issue its certificates.
- MTA-STS0/2
No MTA-STS: mail to the domain can be read in transit by stripping its encryption.
- TLS reporting0/0.5
No TLS reporting: failed encrypted deliveries go unnoticed.
- DKIM
No DKIM key at the common selectors; it may use one that cannot be guessed.
- SPF-all5/5
SPF lists the servers allowed to send its mail and rejects the rest (-all).
- DMARCreject7/7
DMARC tells receivers to reject mail that fakes the domain (p=reject).
Web & network
50/100D- Content Security Policypartial1.5/3
A Content Security Policy is sent, but it does not limit scripts.
- X-Content-Type-Options0/2
No X-Content-Type-Options: browsers may run an upload as a script.
- Referrer-Policy0/0.5
No Referrer-Policy of its own (browsers' default applies).
- IPv60/4
www.chase.com has no IPv6 address: IPv6-only networks reach it only through translation.
- Framing2/2
Other sites cannot frame its pages (clickjacking protection).
- Permissions-Policy0.5/0.5
Permissions-Policy turns off browser features the site does not use.
- RPKIvalid4/4
The route to the website is RPKI-valid: networks can reject hijacked announcements of it.
Dependencies
100/100A+- DNS providersCloudflare, jpmorganchase.com5/5
DNS is served by 2 providers: one can fail without taking the domain offline.
- One company for everything5/5
The website, DNS and email do not all hang on one company.
Who runs it
- Website
- Akamai
- DNS
- Cloudflare jpmorganchase.com
- Broadcom Email Security
Routes
- 80.239.128.0/19AS1299RPKI valid
Name servers
- ns0119.secondary.cloudflare.comCloudflareAS13335
- ns0140.secondary.cloudflare.comCloudflareAS13335
- ns05.jpmorganchase.comjpmorganchase.comAS3486
- ns06.jpmorganchase.comjpmorganchase.comAS3486
- ns1.jpmorganchase.comjpmorganchase.comAS3486
- ns2.jpmorganchase.comjpmorganchase.comAS3486
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/chase.com)Compare with…
What is graded
A valid certificate (an invalid one means F), its expiry against its lifetime, TLS 1.3, no TLS 1.0/1.1 (else at most B), http:// sent straight to https://, HSTS, HTTP/2.
At least two name servers that all answer and agree, DNSSEC, CAA records, and a registration that is not about to expire.
SPF, a DMARC policy that rejects forgeries (none means at most B), MTA-STS and TLS reporting for domains that take mail, DKIM at common selectors.
Content Security Policy, nosniff, framing protection, Referrer- and Permissions-Policy, IPv6, and an RPKI-valid route (invalid means at most C).
DNS from more than one provider, and the website, DNS and email not all with one company.
A+ 95–100 · A 85–94 · B 75–84 · C 65–74 · D 50–64 · F below 50