duck.ai

Readiness by lane

Green: duck.ai. Thin bar: Generative AI Chatbots & Assistants peer median.

Priority fixes for duck.ai

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   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

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.duck.ai.

   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.

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

   Guide: A Practical Website Health Check for Owners

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

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

   Guide: CDN Guide for Website Owners

4. Priority 4 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

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

   Guide: Structured Data Basics for Website Owners

What duck.ai already does well

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

• Referrer-Policy setReferrer-Policy present.35% of peers
• Content Security Policy presentContent-Security-Policy present.40% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.44% of peers

What we saw

Homepage checked

https://duck.ai/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-01

DNS operators

NS1

HSTS

max-age 0 days

Homepage HTML

26 KB, br

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

• chat-box.ai72
• manus.im75
• monica.im75
• speechify.com75
• use.ai72

Generative AI Chatbots & Assistants readiness benchmark