cdc.gov
HTTPS & TLS
100/100A+- HTTPS certificateDigiCert Inc10/10
HTTPS with a valid certificate from DigiCert Inc.
- Certificate expiry654/4
The certificate is valid for another 65 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://.
- 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.
- 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).
- DKIMselector12/2
A DKIM key is published (selector selector1), so its mail can be signed.
Web & network
50/100D- Content Security Policy0/3
No Content Security Policy: an injected script runs with the page's full rights.
- X-Content-Type-Options0/2
No X-Content-Type-Options: browsers may run an upload as a script.
- Framing0/2
Any site can show its pages in a frame, which enables clickjacking.
- 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.
- IPv64/4
www.cdc.gov 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
- fireeyegov.com
Routes
- 2.16.174.0/23AS16625RPKI valid
- 2a02:26f0:3780::/48AS20940RPKI valid
Name servers
- a1-43.akam.netAkamai Edge DNSAS21342
- a2-64.akam.netAkamai Edge DNSAS21342
- a28-65.akam.netAkamai Edge DNSAS21342
- a5-66.akam.netAkamai Edge DNSAS21342
- a8-67.akam.netAkamai Edge DNSAS21342
- a9-64.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/cdc.gov)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