zippybus.com

Readiness by lane

Green: zippybus.com. Thin bar: Trains & Public Transport peer median.

Priority fixes for zippybus.com

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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   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

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   62% of Trains & Public Transport peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

3. Priority 3 · 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 Amazon CloudFront: Set frame options in a response headers policy.

   55% of Trains & Public Transport peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   34% of Trains & Public Transport peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What zippybus.com already does well

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

• HTTP/3 advertisedHTTP/3 advertised.28% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.38% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.40% of peers

What we saw

Homepage checked

https://zippybus.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2026-11-21

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

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 Trains & Public Transport sites

• autogari.ro64
• europodroze.pl67
• garesetconnexions.sncf66
• greyhound.com64
• turbus.cl66

Trains & Public Transport readiness benchmark