paquetexpress.com.mx

Readiness by lane

Green: paquetexpress.com.mx. Thin bar: Postage & Courier Services peer median.

Priority fixes for paquetexpress.com.mx

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from DigiCert Inc was due to expire on 2026-11-03 (11 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

   98% of Postage & Courier Services 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 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   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.

   On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.

   86% of Postage & Courier Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

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

   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

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   44% of Postage & Courier Services peers do this.

   Guide: Browser Caching Guide for Website Owners

What paquetexpress.com.mx already does well

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

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.16% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers
• Content Security Policy presentContent-Security-Policy present.31% of peers

What we saw

Homepage checked

https://www.paquetexpress.com.mx/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

DigiCert, 382-day validity, expiring 2026-11-03

Platform or framework

Nuxt

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

191 KB, gzip

Images on homepage

17 (svg 5, png 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 Postage & Courier Services sites

• delhivery.com58
• kuronekoyamato.co.jp58
• ontrac.com58
• posindonesia.co.id58
• ppl.cz58

Postage & Courier Services readiness benchmark