notebook.google

Readiness by lane

Green: notebook.google. Thin bar: Generative AI Chatbots & Assistants peer median.

Priority fixes for notebook.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.

   46% of Generative AI Chatbots & Assistants 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

   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.

   11% of Generative AI Chatbots & Assistants peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Harden

   DNSSEC signed

   Observed: No DS record was found for notebook.google at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   7.4% of Generative AI Chatbots & Assistants peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

4. Priority 4 · Harden

   Referrer-Policy set

   Observed: The homepage response did not include a Referrer-Policy header.

   What to do: Send Referrer-Policy: strict-origin-when-cross-origin unless you have a reason to share more.

   35% of Generative AI Chatbots & Assistants peers do this.

   Guide: A Practical Website Health Check for Owners

What notebook.google already does well

Practices fewer than half of Generative AI Chatbots & Assistants peers use.

• CAA records limit who can issue certificatesCAA limits issuance to pki.goog.28% of peers
• HTTP/3 advertisedHTTP/3 advertised.37% of peers
• Content Security Policy presentContent-Security-Policy present.40% of peers

What we saw

Homepage checked

https://notebook.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

Google Cloud DNS

DMARC policy

p=reject

Homepage HTML

115 KB, gzip

Images on homepage

0

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 Generative AI Chatbots & Assistants sites

• claude.com84
• openrouter.ai84
• sarvam.ai91
• venice.ai89
• wisprflow.ai89

Generative AI Chatbots & Assistants readiness benchmark