inegi.org.mx

Readiness by lane

Green: inegi.org.mx. Thin bar: Data & Analytics peer median.

Priority fixes for inegi.org.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 Sectigo Limited was due to expire on 2026-11-04 (12 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.

   99% of Data & Analytics 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 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   86% of Data & Analytics peers do this.

   Guide: CDN Guide for Website Owners

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

   49% of Data & Analytics peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Harden

   HSTS kept for at least a year

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

   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.

   34% of Data & Analytics peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What inegi.org.mx already does well

Practices fewer than half of Data & Analytics peers use.

• Modern image formats in useWebP or AVIF images detected.31% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.38% of peers

What we saw

Homepage checked

https://www.inegi.org.mx/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

Sectigo, 372-day validity, expiring 2026-11-04

DNS operators

Azure DNS

DMARC policy

p=reject

Homepage HTML

150 KB, gzip

Images on homepage

12 (png 8, svg 4, webp 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 Data & Analytics sites

• financialjuice.com39
• research-panel.jp37
• tgnmob.ir41
• the-numbers.com38
• worthpoint.com44

Data & Analytics readiness benchmark