msn.com
HTTPS & TLS
100/100A+- HTTPS certificateMicrosoft Corporation10/10
HTTPS with a valid certificate from Microsoft Corporation.
- Certificate expiry1144/4
The certificate is valid for another 114 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://.
- HSTS2 years4/4
HSTS tells browsers to use HTTPS only, for 2 years.
- 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 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.
- CAA recordsglobalsign.com, microsoft.com, digicert.com2/2
CAA records name the authorities allowed to issue its certificates.
- SPF71/5
SPF needs 7 DNS lookups (at most 10 are allowed), so it fails at receivers.
Flatten includes you no longer use, or replace them with ip4:/ip6: ranges.
- 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.
- DKIMselector12/2
A DKIM key is published (selector selector1), so its mail can be signed.
Web & network
69/100C- 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.
- IPv60/4
www.msn.com has no IPv6 address: IPv6-only networks reach it only through translation.
- 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).
- RPKIvalid4/4
The route to the website is RPKI-valid: networks can reject hijacked announcements of it.
Dependencies
100/100A+- DNS providersNS1, Azure DNS5/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
- NS1Azure DNS
- Microsoft 365
Routes
- 23.208.18.0/23AS16625RPKI valid
Name servers
- dns1.p08.nsone.netNS1AS62597
- dns2.p08.nsone.netNS1AS62597
- dns3.p08.nsone.netNS1AS62597
- dns4.p08.nsone.netNS1AS62597
- ns1-204.azure-dns.comAzure DNSAS8075
- ns2-204.azure-dns.netAzure DNSAS8075
- ns3-204.azure-dns.orgAzure DNSAS8075
- ns4-204.azure-dns.infoAzure DNSAS8075
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/msn.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