procuraduria.gov.co

Readiness by lane

Green: procuraduria.gov.co. Thin bar: Government Services peer median.

Priority fixes for procuraduria.gov.co

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-10-29 (6 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 Government 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.

   77% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   55% of Government Services peers do this.

   Guide: CDN 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.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What procuraduria.gov.co already does well

Practices fewer than half of Government Services peers use.

• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers
• Content Security Policy presentContent-Security-Policy present.41% of peers
• Canonical URL declaredCanonical link present.41% of peers

What we saw

Homepage checked

https://www.procuraduria.gov.co/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.2, http/1.1

Certificate

DigiCert, 198-day validity, expiring 2026-10-29

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

80 KB, gzip

Images on homepage

19 (png 15)

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 Government Services sites

• carpetaciudadana.gob.es39
• imss.gob.mx40
• indianvisa-bangladesh.nic.in40
• my.gov.il40
• supremecourt.gov.np40

Government Services readiness benchmark