kogda.by

Readiness by lane

Green: kogda.by. Thin bar: Trains & Public Transport peer median.

Priority fixes for kogda.by

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for kogda.by was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 69 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.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   28% of Trains & Public Transport peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

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

4. Priority 4 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

   54% of Trains & Public Transport peers do this.

   Guide: SEO Checklist for a New Website

What kogda.by already does well

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

• HTTP/3 advertisedHTTP/3 advertised.28% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers
• Structured data presentJSON-LD structured data found.33% of peers

What we saw

Homepage checked

https://kogda.by/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-06

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

125 KB, br

Images on homepage

69 (svg 63, png 5)

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

• at-bus.it78
• egytrains.com78
• jakdojade.pl78
• mta.info78
• railmitra.com78

Trains & Public Transport readiness benchmark