vero.fi

Readiness by lane

Green: vero.fi. Thin bar: Government Services peer median.

Priority fixes for vero.fi

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: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.

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

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for vero.fi, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   17% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What vero.fi already does well

Practices fewer than half of Government Services peers use.

• security.txt publishedsecurity.txt with a contact found.8% of peers
• Social preview image setog:image present.36% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://www.vero.fi/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

DigiCert, 396-day validity, expiring 2027-03-01

DNS operators

Azure DNS

HSTS

max-age 183 days

DMARC policy

p=reject

Homepage HTML

123 KB, gzip

Images on homepage

1 (svg 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 Government Services sites

• bnsp.go.id67
• camara.leg.br67
• portaldatransparencia.gov.br68
• rajasthan.gov.in68
• tjmg.jus.br68

Government Services readiness benchmark