ecorbbs.in

Readiness by lane

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

Priority fixes for ecorbbs.in

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

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

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 ecorbbs.in already does well

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

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.40% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.43% of peers

What we saw

Homepage checked

https://ecorbbs.in/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GoDaddy, 288-day validity, expiring 2026-12-09

DNS operators

GoDaddy DNS

DMARC policy

p=quarantine

Homepage HTML

8 KB, gzip

Images on homepage

1 (jpg 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

• cotralspa.it40
• ctabustracker.com40
• jrkyushu.co.jp40
• tnstc.in41
• varnatraffic.com40

Trains & Public Transport readiness benchmark