camp-fire.jp

Readiness by lane

Green: camp-fire.jp. Thin bar: Crowdfunding Platforms peer median.

Priority fixes for camp-fire.jp

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for camp-fire.jp was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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.

   54% of Crowdfunding Platforms peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for 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.

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

   35% of Crowdfunding Platforms peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.

   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.

   Guide: HTTPS and TLS Guide for Website Owners

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

   33% of Crowdfunding Platforms peers do this.

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

What camp-fire.jp already does well

Practices fewer than half of Crowdfunding Platforms peers use.

• Modern image formats in useWebP or AVIF images detected.40% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers
• Structured data presentJSON-LD structured data found.46% of peers

What we saw

Homepage checked

https://camp-fire.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-04-07

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

DMARC policy

p=none

Homepage HTML

648 KB, gzip

Images on homepage

160 (jpg 74, png 64, svg 9)

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

• boosty.to68
• cafecito.app69
• patreon.com72
• rifa.digital73
• zeffy.com72

Crowdfunding Platforms readiness benchmark