otter.ai

Readiness by lane

Green: otter.ai. Thin bar: Workplace Productivity peer median.

Priority fixes for otter.ai

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.

   90% of Workplace Productivity peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. 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.

   59% of Workplace Productivity peers do this.

   Guide: HTTPS and TLS Guide for Website 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.

   On Cloudflare: Add the header with a response header transform rule.

   52% of Workplace Productivity peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Content Security Policy present

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

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Webflow: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   41% of Workplace Productivity peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What otter.ai already does well

Practices fewer than half of Workplace Productivity peers use.

• HTTP/3 advertisedHTTP/3 advertised.27% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers
• Modern image formats in useWebP or AVIF images detected.49% of peers

What we saw

Homepage checked

https://otter.ai/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2026-12-30

CDN or edge

Cloudflare

Platform or framework

Webflow

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

211 KB, gzip

Images on homepage

86 (avif 98, png 38, svg 21, jpg 3)

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 Workplace Productivity sites

• aladdin.ie66
• fwcms.com.my66
• hrmos.co66
• opluswork.com65
• skyroom.online66

Workplace Productivity readiness benchmark