google.com
HTTPS & TLS
69/100C- HTTP → HTTPS0/3
http://google.com serves the site without encryption instead of redirecting to HTTPS.
Answer every plain-HTTP request with a 301 redirect to the same address on https://.
- Old protocolsTLS 1.10/3
Still accepts TLS 1.1, retired by browsers in 2020 and open to downgrade attacks.
- HSTS0/4
No HSTS: a visitor's first request can be downgraded to plain HTTP.
- HTTPS certificateGoogle Trust Services10/10
HTTPS with a valid certificate from Google Trust Services.
- Certificate expiry584/4
The certificate is valid for another 58 days.
- TLS versionTLS 1.34/4
Negotiates TLS 1.3, the current protocol: faster handshakes, forward secrecy always.
- Key strengthECDSA P-2562/2
A strong key: ECDSA P-256.
- HTTP/2 and HTTP/3HTTP/32/2
HTTP/2 and HTTP/3.
DNS
79/100B- DNSSEC0/3
Not signed with DNSSEC: a forged DNS answer for the domain cannot be told from the real one.
- Name servers44/4
4 name servers for the domain.
- Name servers answer4/45/5
Every name server answers for the domain, with the same version of the zone.
- CAA recordspki.goog2/2
CAA records name the authorities allowed to issue its certificates.
- SPF~all4/5
SPF lists the servers allowed to send its mail and marks the rest as suspicious (~all).
- DMARCreject7/7
DMARC tells receivers to reject mail that fakes the domain (p=reject).
- MTA-STSenforce2/2
MTA-STS makes senders deliver mail to it only over verified TLS.
- TLS reporting0.5/0.5
TLS reporting: senders report failed encrypted deliveries.
- DKIM202306012/2
A DKIM key is published (selector 20230601), so its mail can be signed.
Web & network
69/100C- Content Security Policyreport-only1/3
A Content Security Policy is only reported on, not enforced.
- 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
www.google.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
- About Google
- DNS
- Self-hosted
- Google Workspace
Routes
- 142.251.156.0/24AS15169RPKI valid
- 2001:4860:482d::/48AS15169RPKI valid
Name servers
- ns1.google.comSelf-hostedAS15169
- ns2.google.comSelf-hostedAS15169
- ns3.google.comSelf-hostedAS15169
- ns4.google.comSelf-hostedAS15169
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/google.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