safety.google

Readiness by lane

Green: safety.google. Thin bar: Passwords & Cybersecurity peer median.

Priority fixes for safety.google

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   67% of Passwords & Cybersecurity peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for safety.google was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   65% of Passwords & Cybersecurity peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   67% of Passwords & Cybersecurity peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   29% of Passwords & Cybersecurity peers do this.

   Guide: A Practical Website Health Check for Owners

What safety.google already does well

Practices fewer than half of Passwords & Cybersecurity peers use.

• HTTP/3 advertisedHTTP/3 advertised.33% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
• Reachable over IPv6IPv6 address published.43% of peers

What we saw

Homepage checked

https://safety.google/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 83-day validity, expiring 2026-12-21

CDN or edge

Google edge

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

195 KB, gzip

Images on homepage

57 (svg 73)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Passwords & Cybersecurity sites

• adsblocks.com87
• hcaptcha.com81
• malwarebytes.com88
• totaladblock.com79
• virustotal.com76

Passwords & Cybersecurity readiness benchmark