brightside.me

Readiness by lane

Green: brightside.me. Thin bar: Online Publishing peer median.

Priority fixes for brightside.me

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

   27% of Online Publishing 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.brightside.me.

   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.

   20% of Online Publishing 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.

   41% of Online Publishing peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GoDaddy.com, Inc. had a 397-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.

   71% of Online Publishing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What brightside.me already does well

Practices fewer than half of Online Publishing peers use.

• Referrer-Policy setReferrer-Policy present.20% of peers
• Framing restrictedFraming controls present.37% of peers
• Modern image formats in useWebP or AVIF images detected.38% of peers

What we saw

Homepage checked

https://brightside.me/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 397-day validity, expiring 2027-01-27

DNS operators

Amazon Route 53

HSTS

max-age 180 days, includeSubDomains

Homepage HTML

869 KB, gzip

Images on homepage

47 (webp 72, jpg 72, png 6, svg 4)

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 Online Publishing sites

• capibaratraductor.com70
• collective.world70
• housedigest.com71
• magerta.ir71
• tennenseikatsu.jp71

Online Publishing readiness benchmark