srf.ch

Readiness by lane

Green: srf.ch. Thin bar: News & Media peer median.

Priority fixes for srf.ch

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.

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

   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 News & Media peers do this.

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

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for srf.ch, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   13% of News & Media peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for srf.ch at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   On Amazon Route 53: Enable DNSSEC signing for the hosted zone and establish the chain of trust at the registrar.

   6.1% of News & Media peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What srf.ch already does well

Practices fewer than half of News & Media peers use.

• security.txt publishedsecurity.txt with a contact found.6.2% of peers
• Nameservers spread across providersNameservers spread across Amazon Route 53 and NS1.11% of peers
• Referrer-Policy setReferrer-Policy present.22% of peers

What we saw

Homepage checked

https://www.srf.ch/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Akamai

DNS operators

Amazon Route 53, NS1

HSTS

max-age 30 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

374 KB, br

Images on homepage

101 (webp 46, svg 19)

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

• algerie360.com87
• beebom.com87
• rtvdrenthe.nl88
• rtvnoord.nl88
• spotmedia.ro88

News & Media readiness benchmark