vakinha.com.br

Readiness by lane

Green: vakinha.com.br. Thin bar: Crowdfunding Platforms peer median.

Priority fixes for vakinha.com.br

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

1. Priority 1 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from GlobalSign nv-sa had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   Why it matters: Under CA/Browser Forum Ballot SC-081v3, the maximum lifetime of public TLS certificates fell to 200 days on 15 March 2026 and falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Sites that renew by hand will need to renew far more often.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   75% of Crowdfunding Platforms 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 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   33% of Crowdfunding Platforms peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   29% of Crowdfunding Platforms peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for vakinha.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.

   13% of Crowdfunding Platforms peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What vakinha.com.br already does well

Practices fewer than half of Crowdfunding Platforms peers use.

• Nameservers spread across providersNameservers spread across more than one operator.6.3% of peers
• Referrer-Policy setReferrer-Policy present.31% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.35% of peers

What we saw

Homepage checked

https://www.vakinha.com.br/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 198-day validity, expiring 2027-02-16

Platform or framework

Next.js

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

113 KB, gzip

Images on homepage

2 (png 8)

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 Crowdfunding Platforms sites

• 32auctions.com82
• buymeacoffee.com81
• furuke.com74
• impactguru.com91
• theanimalrescuesite.com77

Crowdfunding Platforms readiness benchmark