stone.com.br

Readiness by lane

Green: stone.com.br. Thin bar: Banking & Finance peer median.

Priority fixes for stone.com.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: The homepage response did not include a Strict-Transport-Security header.

   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.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

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

   On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   43% of Banking & Finance peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Amazon CloudFront: Enable it in a response headers policy (security headers section).

   65% of Banking & Finance peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for stone.com.br, 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.

   20% of Banking & Finance peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What stone.com.br already does well

Practices fewer than half of Banking & Finance peers use.

• HTTP/3 advertisedHTTP/3 advertised.22% of peers
• Reachable over IPv6IPv6 address published.26% of peers
• Certificate lifetime of 100 days or lessShort-lived 97-day certificate from GoDaddy.com, already inside the 2027 limit.31% of peers

What we saw

Homepage checked

https://www.stone.com.br/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GoDaddy, 97-day validity, expiring 2027-01-24

CDN or edge

Akamai, Amazon CloudFront

Platform or framework

WordPress

DNS operators

Akamai Edge DNS

DMARC policy

p=reject

Homepage HTML

446 KB, gzip

Images on homepage

172 (svg 74, webp 58, png 55, avif 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

• anz.co.nz79
• bpi.com.ph77
• minfin.com.ua78
• nu.com.co79
• queroquitar.com.br79

Banking & Finance readiness benchmark