sat.gob.pe

Readiness by lane

Green: sat.gob.pe. Thin bar: Government Services peer median.

Priority fixes for sat.gob.pe

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

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

   55% of Government Services peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for sat.gob.pe 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 Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   42% of Government Services peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

What sat.gob.pe already does well

Practices fewer than half of Government Services peers use.

• Social preview image setog:image present.36% of peers
• Offscreen images lazy-loadedNative lazy loading in use.36% of peers
• Referrer-Policy setReferrer-Policy present.39% of peers

What we saw

Homepage checked

https://www.sat.gob.pe/

Homepage response

HTTP 200, after 3 redirects

TLS

TLSv1.2

Certificate

Sectigo, 198-day validity, expiring 2027-03-27

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 730 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

272 KB, gzip

Images on homepage

19 (png 8, jpg 7, svg 4)

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

• police.hu52
• policia.gov.co52
• rosario.gob.ar52
• sepe.es52
• sgc.gov.co52

Government Services readiness benchmark