indianrail.gov.in

Readiness by lane

Green: indianrail.gov.in. Thin bar: Trains & Public Transport peer median.

Priority fixes for indianrail.gov.in

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

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

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   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. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   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.

   Guide: HTTPS and TLS Guide for Website Owners

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

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

What indianrail.gov.in already does well

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

• Nameservers spread across providersNameservers spread across more than one operator.15% of peers
• Content Security Policy presentContent-Security-Policy present.34% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.40% of peers

What we saw

Homepage checked

https://www.indianrail.gov.in/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.2

Certificate

GlobalSign, 396-day validity, expiring 2026-12-19

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 186 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

12 KB, gzip

Images on homepage

4 (gif 4)

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

• apsrtconline.in41
• hankyu.co.jp42
• kuruken.jp41
• lefrecce.it41
• menetrendek.hu42

Trains & Public Transport readiness benchmark