zditm.szczecin.pl

Readiness by lane

Green: zditm.szczecin.pl. Thin bar: Trains & Public Transport peer median.

Priority fixes for zditm.szczecin.pl

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.zditm.szczecin.pl.

   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

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   43% of Trains & Public Transport peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for zditm.szczecin.pl, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   8.9% of Trains & Public Transport peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for zditm.szczecin.pl at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   13% of Trains & Public Transport peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What zditm.szczecin.pl already does well

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

• security.txt publishedsecurity.txt with a contact found.9.5% of peers
• HTTP/3 advertisedHTTP/3 advertised.28% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers

What we saw

Homepage checked

https://www.zditm.szczecin.pl/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-01

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 730 days

Homepage HTML

123 KB, gzip

Images on homepage

2 (svg 2)

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

• buser.com.br91
• eurostar.com90
• infobus.eu79
• ns.nl84
• pamukkale.com.tr79

Trains & Public Transport readiness benchmark