caixa.gov.br

Readiness by lane

Green: caixa.gov.br. Thin bar: Banking & Finance peer median.

Priority fixes for caixa.gov.br

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   62% of Banking & Finance peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 days, 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.

   43% of Banking & Finance peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Enable

   At most one redirect to the homepage

   Observed: The homepage was reached after 2 redirects.

   What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

   97% of Banking & Finance peers do this.

   Guide: Technical SEO Audit: A Practical Owner’s Guide

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 7 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   36% of Banking & Finance peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What caixa.gov.br already does well

Practices fewer than half of Banking & Finance peers use.

• CAA records limit who can issue certificatesCAA limits issuance to certificados.serpro.gov.br, digicert.com, globalsign.com and others.20% of peers
• Nameservers spread across providersNameservers spread across more than one operator.21% of peers
• Modern image formats in useWebP or AVIF images detected.37% of peers

What we saw

Homepage checked

https://www.caixa.gov.br/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 198-day validity, expiring 2026-11-29

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 0 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

290 KB, gzip

Images on homepage

45 (png 26, jpg 18, webp 1)

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 Banking & Finance sites

• creditmutuel.fr69
• davibank.com69
• mercantilbanco.com70
• openbank.mx70
• tangerine.ca70

Banking & Finance readiness benchmark