cloudflare.com
HTTPS & TLS
100/100A+- HTTPS certificateGoogle Trust Services10/10
HTTPS with a valid certificate from Google Trust Services.
- Certificate expiry884/4
The certificate is valid for another 88 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 year4/4
HSTS tells browsers to use HTTPS only, for 1 year.
- HTTP/2 and HTTP/3HTTP/32/2
HTTP/2 and HTTP/3.
DNS
100/100A+- Name servers54/4
5 name servers for the domain.
- Name servers answer5/55/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.
- CAA recordscomodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com2/2
CAA records name the authorities allowed to issue its certificates.
- MTA-STSpolicy_unreachable0/2
MTA-STS is announced, but its policy file cannot be used.
Serve https://mta-sts.cloudflare.com/.well-known/mta-sts.txt with a valid certificate.
- 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).
- TLS reporting0.5/0.5
TLS reporting: senders report failed encrypted deliveries.
- 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-Policystrict-origin-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.cloudflare.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
80/100B- DNS providersSelf-hosted3/5
All DNS is with one provider (Self-hosted): an outage there takes the domain offline, as Dyn's did in 2016.
- One company for everything5/5
The website, DNS and email do not all hang on one company.
Who runs it
- Website
- Cloudflare
- DNS
- Self-hosted
- cf-emailsecurity.net
Routes
- 104.16.112.0/20AS13335RPKI valid
- 2606:4700::/44AS13335RPKI valid
Name servers
- ns3.cloudflare.comSelf-hostedAS13335
- ns4.cloudflare.comSelf-hostedAS13335
- ns5.cloudflare.comSelf-hostedAS13335
- ns6.cloudflare.comSelf-hostedAS13335
- ns7.cloudflare.comSelf-hostedAS13335
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/cloudflare.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