orf.at

Readiness by lane

Green: orf.at. Thin bar: News & Media peer median.

Priority fixes for orf.at

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.

   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 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   87% of News & Media peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

3. Priority 3 · 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.

   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.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 25 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.

   44% of News & Media peers do this.

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

What orf.at 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 more than one operator.11% of peers
• Referrer-Policy setReferrer-Policy present.22% of peers

What we saw

Homepage checked

https://orf.at/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GlobalSign, 198-day validity, expiring 2027-01-03

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 30 days

DMARC policy

p=quarantine

Homepage HTML

93 KB, gzip

Images on homepage

25 (jpg 60, svg 16)

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

• nzz.ch69
• onetz.de69
• onlarissa.gr69
• ostsee-zeitung.de69
• ozap.com69

News & Media readiness benchmark