Website readiness profile · Snapshot 23 October 2026
opencode.ai
opencode.ai's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.
- Readiness index
- 62/100
- Ahead of
- 34%
- Practices observed
- 17/29
- Popularity band
- Top 50K
Programming & Software median 68
of measured Programming & Software sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: opencode.ai. Thin bar: Programming & Software peer median.
Enable
92/100
Peers 81
Harden
34/100
Peers 59
Accelerate
87/100
Peers 65
Recover
0/100
Peers 7
Priority fixes for opencode.ai
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://opencode.ai/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
On Cloudflare: Turn on Always Use HTTPS under SSL/TLS > Edge Certificates.
92% of Programming & Software peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
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.
40% of Programming & Software peers do this.
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for opencode.ai 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.
45% of Programming & Software peers do this.
Priority 4 · 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.
On Cloudflare: Add the header with a response header transform rule.
47% of Programming & Software peers do this.
What opencode.ai already does well
Practices fewer than half of Programming & Software peers use.
- CAA records limit who can issue certificatesCAA limits issuance to amazonaws.com, comodoca.com, digicert.com and others.23% of peers
What we saw
- Homepage checked
- https://opencode.ai/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-19
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- DMARC policy
- p=none
- Homepage HTML
- 69 KB, br
- Images on homepage
- 2
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 12
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Structured data present
- Nameservers spread across providers
Observed 17
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own opencode.ai?
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: opencode.ai. This profile covers configuration only.