Infrastructure report cardTop 5K site

washingtonpost.com

75 out of 10015 passed6 to improve

Checked yesterday· Grading…

HTTPS & TLSA

Certificate, protocol, redirect, HSTS88

DNSD

Name servers, DNSSEC, CAA, registration57

EmailA

SPF, DMARC, MTA-STS, DKIM85

Web & networkD

Security headers, IPv6, RPKI50

DependenciesA⁺

How much hangs on one company100

HTTPS & TLS

88/100A

HSTS0/4
No HSTS: a visitor's first request can be downgraded to plain HTTP.
HTTPS certificateAmazon10/10
HTTPS with a valid certificate from Amazon.
Certificate expiry1674/4
The certificate is valid for another 167 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://.
HTTP/2 and HTTP/3HTTP/22/2
HTTP/2.

DNS

57/100D

Name servers answer4/82/5
4 of 8 name servers answer for the domain; the others leave resolvers waiting.
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.
CAA recordsamazonaws.com, amazontrust.com, awstrust.com, entrust.net, pki.goog, amazon.com2/2
CAA records name the authorities allowed to issue its certificates.

Email

85/100A

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).
DMARCreject7/7
DMARC tells receivers to reject mail that fakes the domain (p=reject).
DKIMzendesk12/2
A DKIM key is published (selector zendesk1), so its mail can be signed.

Web & network

50/100D

IPv60/4
washingtonpost.com has no IPv6 address: IPv6-only networks reach it only through translation.
Security headers
The website did not answer the check, so its headers are not graded.
RPKIvalid4/4
The route to the website is RPKI-valid: networks can reject hijacked announcements of it.

Dependencies

100/100A⁺

DNS providersAmazon Route 53, UltraDNS5/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: Amazon CloudFront
DNS: Amazon Route 53 UltraDNS
Email: Proofpoint

Routes

3.164.224.0/21AS16509RPKI valid

Name servers

ns-1027.awsdns-00.orgAmazon Route 53AS16509
ns-1840.awsdns-38.co.ukAmazon Route 53AS16509
ns-404.awsdns-50.comAmazon Route 53AS16509
ns-666.awsdns-19.netAmazon Route 53AS16509
sdns34.ultradns.bizUltraDNSAS12008
sdns34.ultradns.comUltraDNSAS12008
sdns34.ultradns.netUltraDNSAS12008
sdns34.ultradns.orgUltraDNSAS12008

README badge

Show the grade in your README or docs; it updates when the domain is graded again.

[![Infrastructure grade](https://skycisa.com/grade/washingtonpost.com/badge.svg)](https://skycisa.com/grade/washingtonpost.com)

Compare with…

Full lookup

What is graded

HTTPS & TLS · 25%

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.

DNS · 20%

At least two name servers that all answer and agree, DNSSEC, CAA records, and a registration that is not about to expire.

Email · 20%

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.

Web & network · 20%

Content Security Policy, nosniff, framing protection, Referrer- and Permissions-Policy, IPv6, and an RPKI-valid route (invalid means at most C).

Dependencies · 15%

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