bahn.de

Readiness by lane

Green: bahn.de. Thin bar: Trains & Public Transport peer median.

Priority fixes for bahn.de

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.

   41% of Trains & Public Transport 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 · 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.

   66% of Trains & Public Transport peers do this.

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

3. Priority 3 · Accelerate

   Modern image formats in use

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

   28% of Trains & Public Transport peers do this.

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

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

   28% of Trains & Public Transport peers do this.

   Guide: CDN Guide for Website Owners

What bahn.de already does well

Practices fewer than half of Trains & Public Transport peers use.

• security.txt publishedsecurity.txt with a contact found.9.5% of peers
• Reachable over IPv6IPv6 address published.33% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers

What we saw

Homepage checked

https://www.bahn.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Akamai

DNS operators

Amazon Route 53

HSTS

max-age 183 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

59 KB, br

Images on homepage

14 (svg 9, jpg 6, 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 Trains & Public Transport sites

• carrismetropolitana.pt74
• interrail.com75
• kbuses.in76
• thetrainline.com76
• vr.fi76

Trains & Public Transport readiness benchmark