radiofrance.fr

Readiness by lane

Green: radiofrance.fr. Thin bar: Audio & Music Streaming peer median.

Priority fixes for radiofrance.fr

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

   33% of Audio & Music Streaming 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: The DMARC policy for radiofrance.fr 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.

   38% of Audio & Music Streaming 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.

   31% of Audio & Music Streaming peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for radiofrance.fr, 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 Audio & Music Streaming peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What radiofrance.fr already does well

Practices fewer than half of Audio & Music Streaming peers use.

• security.txt publishedsecurity.txt with a contact found.10% of peers
• Content Security Policy presentContent-Security-Policy present.18% of peers
• Modern image formats in useWebP or AVIF images detected.34% of peers

What we saw

Homepage checked

https://www.radiofrance.fr/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-06

CDN or edge

Akamai

DNS operators

Amazon Route 53

HSTS

max-age 183 days

DMARC policy

p=none

Homepage HTML

2,106 KB, gzip

Images on homepage

327 (png 1)

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 Audio & Music Streaming sites

• bandlab.com80
• canliradyodinle.fm82
• epidemicsound.com84
• songsterr.com84
• spotify.com81

Audio & Music Streaming readiness benchmark