sepe.es

Readiness by lane

Green: sepe.es. Thin bar: Government Services peer median.

Priority fixes for sepe.es

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

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

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

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

   55% of Government Services peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

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

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for sepe.es 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 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   68% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

What sepe.es already does well

Practices fewer than half of Government Services peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.19% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers
• Social preview image setog:image present.36% of peers

What we saw

Homepage checked

https://www.sepe.es/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3

Certificate

Entrust Limited, 396-day validity, expiring 2027-04-03

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=none

Homepage HTML

106 KB, gzip

Images on homepage

25 (svg 13, jpg 10, png 2)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Government Services sites

• policia.gov.co52
• rosario.gob.ar52
• sat.gob.pe52
• sgc.gov.co52
• swavlambancard.gov.in52

Government Services readiness benchmark