24smi.org

Readiness by lane

Green: 24smi.org. Thin bar: News & Media peer median.

Priority fixes for 24smi.org

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.

   93% of News & Media 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.

   35% of News & Media peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 40 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   44% of News & Media peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for 24smi.org 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.

   37% of News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

What 24smi.org already does well

Practices fewer than half of News & Media peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.13% of peers
• Framing restrictedFraming controls present.42% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers

What we saw

Homepage checked

https://24smi.org/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

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

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

104 KB, gzip

Images on homepage

40 (jpg 57, png 4, svg 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

Compare with other News & Media sites

• aa.com.tr64
• adnradio.cl64
• webnews.it65
• yapolitic.net65
• zdg.md65

News & Media readiness benchmark