espn.com
HTTPS & TLS
69/100C- HTTP → HTTPS0/3
http://espn.com serves the site without encryption instead of redirecting to HTTPS.
Answer every plain-HTTP request with a 301 redirect to the same address on https://.
- Old protocolsTLS 1.10/3
Still accepts TLS 1.1, retired by browsers in 2020 and open to downgrade attacks.
- HSTS0/4
No HSTS: a visitor's first request can be downgraded to plain HTTP.
- HTTPS certificateSectigo Limited10/10
HTTPS with a valid certificate from Sectigo Limited.
- Certificate expiry284/4
The certificate is valid for another 28 days.
- TLS versionTLS 1.34/4
Negotiates TLS 1.3, the current protocol: faster handshakes, forward secrecy always.
- Key strengthRSA 20482/2
A strong key: RSA 2048.
- HTTP/2 and HTTP/3HTTP/22/2
HTTP/2.
DNS
64/100D- DNSSEC0/3
Not signed with DNSSEC: a forged DNS answer for the domain cannot be told from the real one.
- CAA records0/2
No CAA records: any certificate authority may issue certificates for the domain.
- Name servers44/4
4 name servers for the domain.
- Name servers answer4/45/5
Every name server answers for the domain, with the same version of the zone.
- DMARCnone2/7
DMARC only watches (p=none): mail that fakes the domain is still delivered.
- 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.
- SPF~all4/5
SPF lists the servers allowed to send its mail and marks the rest as suspicious (~all).
- DKIMselector12/2
A DKIM key is published (selector selector1), so its mail can be signed.
Web & network
50/100D- Content Security Policy0/3
No Content Security Policy: an injected script runs with the page's full rights.
- X-Content-Type-Options0/2
No X-Content-Type-Options: browsers may run an upload as a script.
- Framing0/2
Any site can show its pages in a frame, which enables clickjacking.
- Referrer-Policy0/0.5
No Referrer-Policy of its own (browsers' default applies).
- Permissions-Policy0/0.5
No Permissions-Policy: embedded content may ask for camera, microphone or location.
- IPv64/4
espn.com is reachable over IPv6 as well as IPv4.
- RPKIvalid4/4
The route to the website is RPKI-valid: networks can reject hijacked announcements of it.
Dependencies
60/100D- DNS providersAmazon Route 533/5
All DNS is with one provider (Amazon Route 53): an outage there takes the domain offline, as Dyn's did in 2016.
- One company for everythingAmazon CloudFront: website, DNS3/5
Amazon CloudFront runs both the website and the DNS: one outage there takes both down.
Who runs it
- Website
- Amazon CloudFront
- Microsoft 365
Routes
- 13.249.8.0/21AS16509RPKI valid
- 2600:9000:208a::/48AS16509RPKI valid
Name servers
- ns-1045.awsdns-02.orgAmazon Route 53AS16509
- ns-122.awsdns-15.comAmazon Route 53AS16509
- ns-1936.awsdns-50.co.ukAmazon Route 53AS16509
- ns-846.awsdns-41.netAmazon Route 53AS16509
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/espn.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