railway.gov.tw

Readiness by lane

Green: railway.gov.tw. Thin bar: Trains & Public Transport peer median.

Priority fixes for railway.gov.tw

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from TAIWAN-CA was due to expire on 2026-11-05 (13 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   98% 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 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   77% of Trains & Public Transport peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   81% of Trains & Public Transport peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

4. Priority 4 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 186 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.

   41% of Trains & Public Transport peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What railway.gov.tw already does well

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

• DNSSEC signedDNSSEC delegation (DS record) present.13% of peers
• Structured data presentJSON-LD structured data found.33% of peers
• Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked

https://www.railway.gov.tw/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3

Certificate

TAIWAN-CA, 365-day validity, expiring 2026-11-05

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 186 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

388 KB, gzip

Images on homepage

25 (png 10, svg 4, jpg 2, gif 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Trains & Public Transport sites

• highwaybus.com51
• idos.cz51
• jr-odekake.net53
• poizdato.net52
• rmv.de53

Trains & Public Transport readiness benchmark