Website readiness profile · Snapshot 23 October 2026
bolt.new
bolt.new's public homepage, certificate and DNS checked against 31 practices and compared with 38 Website Builders sites.
- Readiness index
- 79/100
- Ahead of
- 74%
- Practices observed
- 24/31
- Popularity band
- Top 50K
Website Builders median 64
of measured Website Builders sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: bolt.new. Thin bar: Website Builders peer median.
Enable
100/100
Peers 81
Harden
63/100
Peers 58
Accelerate
90/100
Peers 63
Recover
0/100
Peers 5
Priority fixes for bolt.new
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for bolt.new was p=none, which asks receivers to take no action on failing mail.
Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.
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.
61% of Website Builders peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.
Priority 2 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.
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.
On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
26% of Website Builders peers do this.
Priority 3 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
29% of Website Builders peers do this.
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.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
16% of Website Builders peers do this.
What bolt.new already does well
Practices fewer than half of Website Builders peers use.
- Content Security Policy presentContent-Security-Policy present.26% of peers
- Reachable over IPv6IPv6 address published.26% of peers
- Referrer-Policy setReferrer-Policy present.29% of peers
What we saw
- Homepage checked
- https://bolt.new/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-04
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- HSTS
- max-age 180 days
- DMARC policy
- p=none
- Homepage HTML
- 142 KB, br
- Images on homepage
- 18 (svg 13, png 4, webp 1)
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
Not observed 7
Observed 24
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own bolt.new?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: bolt.new. This profile covers configuration only.