radio.garden

Readiness by lane

Green: radio.garden. Thin bar: Audio & Music Streaming peer median.

Priority fixes for radio.garden

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   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

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Cloudflare: Add the header with a response header transform rule.

   42% of Audio & Music Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   52% of Audio & Music Streaming peers do this.

   Guide: Structured Data Basics for Website Owners

4. Priority 4 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Cloudflare: Add the header with a response header transform rule.

   43% of Audio & Music Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

What radio.garden already does well

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

• HTTP/3 advertisedHTTP/3 advertised.31% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.38% of peers
• Reachable over IPv6IPv6 address published.41% of peers

What we saw

Homepage checked

https://radio.garden/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-02

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=reject

Homepage HTML

26 KB, gzip

Images on homepage

0

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

• 1001tracklists.com73
• joysound.com74
• los40.com74
• ondacero.es74
• storytel.com74

Audio & Music Streaming readiness benchmark