17track.net

Readiness by lane

Green: 17track.net. Thin bar: Postage & Courier Services peer median.

Priority fixes for 17track.net

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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

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

   On Next.js: Use the next/script component with an appropriate loading strategy.

   39% of Postage & Courier Services peers do this.

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

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.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   31% of Postage & Courier Services peers do this.

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

4. Priority 4 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Cloudflare: Add the header with a response header transform rule.

   45% of Postage & Courier Services peers do this.

   Guide: A Practical Website Health Check for Owners

What 17track.net already does well

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

• HTTP/3 advertisedHTTP/3 advertised.22% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers
• Structured data presentJSON-LD structured data found.42% of peers

What we saw

Homepage checked

https://www.17track.net/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DNSPod, Inc., 195-day validity, expiring 2027-03-02

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

197 KB, gzip

Images on homepage

57 (png 28, webp 18, svg 8, jpg 3)

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

• dsv.com74
• flety.io73
• lalamove.com73
• lbcexpress.com74
• usps.com74

Postage & Courier Services readiness benchmark