trackcourier.io

Readiness by lane

Green: trackcourier.io. Thin bar: Postage & Courier Services peer median.

Priority fixes for trackcourier.io

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   39% of Postage & Courier Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.trackcourier.io.

   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.

   52% of Postage & Courier Services peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   50% of Postage & Courier Services peers do this.

   Guide: A Practical Website Health Check for Owners

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

   31% of Postage & Courier Services peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What trackcourier.io already does well

Practices fewer than half of Postage & Courier Services peers use.

• Reachable over IPv6IPv6 address published.31% of peers
• Certificate lifetime of 100 days or lessShort-lived 90-day certificate from Google Trust Services, already inside the 2027 limit.39% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://trackcourier.io/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Google edge

DNS operators

GoDaddy DNS

Homepage HTML

73 KB, gzip

Images on homepage

0

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 Postage & Courier Services sites

• chaparnet.com64
• correos.es64
• gls-italy.com65
• indiapost.gov.in66
• shalom.com.pe66

Postage & Courier Services readiness benchmark