cp.sk

Readiness by lane

Green: cp.sk. Thin bar: Trains & Public Transport peer median.

Priority fixes for cp.sk

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.

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

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.cp.sk.

   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 cp.sk already does well

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

• DNSSEC signedDNSSEC delegation (DS record) present.13% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.38% of peers

What we saw

Homepage checked

https://cp.sk/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-04-08

DNS operators

1 self-run or other nameserver domain

Homepage HTML

83 KB, gzip

Images on homepage

5 (png 2)

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

• ctpcj.ro49
• idos.cz51
• indianrailways.gov.in47
• mavcsoport.hu51
• portalpasazera.pl51

Trains & Public Transport readiness benchmark