This report summarizes how well google.com is configured for secure web delivery. It covers HTTPS availability, HTTP→HTTPS redirects, TLS/SSL certificate validity, security headers, HTTP/2 and HTTP/3 support, and mixed content. Use it to quickly spot configuration gaps and improve your site's security and trust.
Enabled
Yes
A · 1.2, 1.3
3/6
The site is reachable over HTTPS.
Why it matters: HTTPS encrypts traffic and protects user data.
Requests to HTTP are redirected to HTTPS.
| Valid | Yes |
| Issuer | C=US, O=Google Trust Services, CN=WR2 |
| Expires | 2026-04-13 |
| Days until expiry | 45 days |
Why it matters: A valid, non-expired certificate ensures encryption is trusted by browsers.
To improve your grade
Get a reminder 30 days before the SSL certificate expires
We’ll send you one email about the expiry, no spam and no subscription.
Requires 4 of 6 headers and Content-Security-Policy (CSP).
To improve your grade
Score: 3 of 6 headers present. For the grade factor (5 pts), 4+ headers and Content-Security-Policy (CSP) are both required.
Why it matters: HSTS tells browsers to use only HTTPS for this site. Preload allows inclusion in browsers’ built-in HSTS lists.
We check Chromium’s built-in list. hstspreload.org checks eligibility for submission (HSTS header, redirect chain). Results may differ for domains that are preloaded but no longer meet current eligibility rules.
Advertised
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Allowed issuers: pki.goog
None detected
No HTTP resources were detected on the HTTPS page.
When you visit the site over HTTP, the server may send you through one or more redirects until you land on the final HTTPS URL. Shorter chains are faster and better for SEO.
Domain owner? If you want this report removed or made private, contact us.