idos.cz

Readiness by lane

Green: idos.cz. Thin bar: Trains & Public Transport peer median.

Priority fixes for idos.cz

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.

   85% of Trains & Public Transport 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 · Harden

   HSTS kept for at least a year

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

   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.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.idos.cz.

   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.

   40% of Trains & Public Transport peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   Modern image formats in use

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

What idos.cz already does well

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

• DNSSEC signedDNSSEC delegation (DS record) present.13% of peers
• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.38% of peers

What we saw

Homepage checked

https://idos.cz/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.2, HTTP/2

Certificate

DigiCert, 184-day validity, expiring 2027-02-14

DNS operators

2 self-run or other nameserver domains

Homepage HTML

91 KB, gzip

Images on homepage

5 (svg 1, gif 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

• highwaybus.com51
• mavcsoport.hu51
• poizdato.net52
• portalpasazera.pl51
• railway.gov.tw52

Trains & Public Transport readiness benchmark