mit.edu
HTTPS & TLS
78/100B- TLS versionTLS 1.22/4
Negotiates TLS 1.2 at best; TLS 1.3 is faster and drops old ciphers.
- HTTP → HTTPS2/3
http:// reaches HTTPS only after another plain-HTTP hop.
- HSTS0 hours2/4
HSTS is on, but only for 0 hours.
- HTTP/2 and HTTP/3HTTP/1.10/2
Only HTTP/1.1: no multiplexing, slower pages.
- HTTPS certificateDigiCert Inc10/10
HTTPS with a valid certificate from DigiCert Inc.
- Certificate expiry314/4
The certificate is valid for another 31 days.
- Old protocols3/3
Refuses the retired TLS 1.0 and 1.1.
- Key strengthRSA 20482/2
A strong key: RSA 2048.
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 servers84/4
8 name servers for the domain.
- Name servers answer8/85/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-all5/5
SPF lists the servers allowed to send its mail and rejects the rest (-all).
- DKIMgoogle2/2
A DKIM key is published (selector google), so its mail can be signed.
Web & network
72/100C- 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).
- Permissions-Policy0/0.5
No Permissions-Policy: embedded content may ask for camera, microphone or location.
- Framing2/2
Other sites cannot frame its pages (clickjacking protection).
- IPv64/4
web.mit.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
60/100D- DNS providersAkamai Edge DNS3/5
All DNS is with one provider (Akamai Edge DNS): an outage there takes the domain offline, as Dyn's did in 2016.
- One company for everythingAkamai: website, DNS3/5
Akamai runs both the website and the DNS: one outage there takes both down.
Who runs it
- Website
- Akamai
- Microsoft 365
Routes
- 23.52.16.0/20AS16625RPKI valid
- 2a02:26f0:3780::/48AS20940RPKI valid
Name servers
- asia1.akam.netAkamai Edge DNSAS21342
- asia2.akam.netAkamai Edge DNSAS21342
- eur5.akam.netAkamai Edge DNSAS21342
- ns1-173.akam.netAkamai Edge DNSAS21342
- ns1-37.akam.netAkamai Edge DNSAS21342
- use2.akam.netAkamai Edge DNSAS21342
- use5.akam.netAkamai Edge DNSAS21342
- usw2.akam.netAkamai Edge DNSAS21342
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/mit.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