stanford.edu
HTTPS & TLS
100/100A+- HTTPS certificateLet's Encrypt10/10
HTTPS with a valid certificate from Let's Encrypt.
- Certificate expiry394/4
The certificate is valid for another 39 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 strengthECDSA P-2562/2
A strong key: ECDSA P-256.
- HTTP → HTTPS3013/3
http:// redirects straight to https://.
- HSTS1 year · preload4/4
HSTS tells browsers to use HTTPS only, for 1 year.
- HTTP/2 and HTTP/3HTTP/22/2
HTTP/2.
DNS
86/100A- CAA records0/2
No CAA records: any certificate authority may issue certificates for the domain.
- 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.
- DNSSECECDSAP256SHA2563/3
Signed with DNSSEC: resolvers can tell forged answers from real ones.
- SPF?all1/5
SPF does not say what to do with other servers (?all neutral).
- 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.
- DMARCquarantine5/7
DMARC sends mail that fakes the domain to spam (p=quarantine).
- DKIMk12/2
A DKIM key is published (selector k1), so its mail can be signed.
Web & network
100/100A+- Content Security Policy3/3
A Content Security Policy limits which scripts the pages run.
- X-Content-Type-Options2/2
X-Content-Type-Options: nosniff stops browsers guessing file types.
- Framing2/2
Other sites cannot frame its pages (clickjacking protection).
- Referrer-Policyorigin-when-cross-origin0.5/0.5
Referrer-Policy limits what other sites learn about where visitors came from.
- Permissions-Policy0.5/0.5
Permissions-Policy turns off browser features the site does not use.
- IPv64/4
www.stanford.edu 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
100/100A+- DNS providersSelf-hosted, DNS Made Easy5/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
- Netlify
- DNS
- Self-hostedDNS Made Easy
- Proofpoint
Routes
- 15.197.160.0/20AS16509RPKI valid
- 2a05:d014:400::/38AS16509RPKI valid
Name servers
- argus.stanford.eduSelf-hostedAS32
- atalante.stanford.eduSelf-hostedAS32
- avallone.stanford.eduSelf-hostedAS32
- ns5.dnsmadeeasy.comDNS Made EasyAS16552
- ns6.dnsmadeeasy.comDNS Made EasyAS16552
- ns7.dnsmadeeasy.comDNS Made EasyAS16552
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/stanford.edu)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