brandcrowd.com

Readiness by lane

Green: brandcrowd.com. Thin bar: Design & Content Creation peer median.

Priority fixes for brandcrowd.com

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

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   37% of Design & Content Creation 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 · 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 Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

   43% of Design & Content Creation peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   72% of Design & Content Creation peers do this.

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

   29% of Design & Content Creation peers do this.

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

What brandcrowd.com already does well

Practices fewer than half of Design & Content Creation peers use.

• Referrer-Policy setReferrer-Policy present.26% of peers
• X-Content-Type-Options: nosniffnosniff header present.39% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.41% of peers

What we saw

Homepage checked

https://www.brandcrowd.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-02-07

CDN or edge

Amazon CloudFront

Platform or framework

Nuxt

DNS operators

Amazon Route 53

HSTS

max-age 30 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

409 KB, gzip

Images on homepage

52 (png 92, webp 56)

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 Design & Content Creation sites

• clideo.com77
• design.com77
• kleki.com78
• myfonts.com78
• pixlr.com78

Design & Content Creation readiness benchmark