Security - https://wefunder.com BeaverCheck Audit

F

Content Security Policy

Action

No enforcing CSP policy found

FIX

No enforcing CSP policy found

No Content-Security-Policy header found

CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

Expected: default-src 'self'

CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

Expected: default-src 'self'

Why this matters

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever. Start in Report-Only mode, fix violations, then graduate to enforcing.

Source: OWASP / MDN

D

security.txt

Action

No /.well-known/security.txt published

FIX

security.txt

No security.txt found at /.well-known/security.txt

B

Security Headers

8 of 10 headers properly configured

REVIEW

8 of 10 headers properly configured

HSTS is missing includeSubDomains

Without includeSubDomains, subdomains can still be accessed over HTTP.

Got: max-age=31536000 Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: SAMEORIGIN

Referrer-Policy is properly configured

Got: same-origin

Permissions-Policy is set

Got: accelerometer=(),browsing-topics=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=(self)

Content-Security-Policy header is missing

CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.

Expected: default-src 'self'

Cross-Origin-Opener-Policy is properly configured

Got: same-origin

Cross-Origin-Embedder-Policy is set

Got: require-corp

X-Powered-By header is not present

Server header is present without version info

Got: cloudflare

CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.

Expected: default-src 'self'

Why this matters

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies or rewrite the page is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever.

Source: OWASP / MDN

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains

Why this matters

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more ▾

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

C

Subresource Integrity

Action

1 of 2 external resources have SRI

REVIEW

1 of 2 external resources have SRI

External script from challenges.cloudflare.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://challenges.cloudflare.com/turnstile/v0/b/0b8fb825cb67/api.js?onload=cFRiY3&render=explicit

script from static.cloudflareinsights.com has SRI protection

SRI Coverage 1 / 2 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	challenges.cloudflare.com	✗ Missing
<script>	static.cloudflareinsights.com	✓ Protected

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

No CORS headers present — secure default

CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control

A+

TLS & Certificates

TLS 1.3, 7 checks passed

PASS

TLS 1.3, 7 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_CHACHA20_POLY1305_SHA256

HTTP/2 is not negotiated

HTTP/2 provides multiplexing and header compression for better performance.

Got: http/1.1

Certificate is valid (expires in 50 days)

Got: 2026-06-12T12:58:58Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA384

Certificate covers 2 domain(s)

Got: *.wefunder.com, wefunder.com

Certificate is issued by a trusted CA

Got: CN=E8,O=Let's Encrypt,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_CHACHA20_POLY1305_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=wefunder.comIssuer CN=E8,O=Let's Encrypt,C=USValid 2026-03-14T12:58:59Z → 2026-06-12T12:58:58ZExpires in 50 days SANs *.wefunder.com, wefunder.comSignature ECDSA-SHA384Serial 5111b4750e4164ab9a11108ee5699fa29e8

Intermediate (CA Certificate)

Subject CN=E8,O=Let's Encrypt,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2024-03-13T00:00:00Z → 2027-03-12T23:59:59ZExpires in 324 days Signature SHA256-RSASerial 63959363c24e7082715918bfc3d7ed56

A+

Cookie Security

No cookies set — no cookie security risks

PASS

No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

No security.txt found

Consider adding a security.txt at /.well-known/security.txt.

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✓ Not found	Security Policy	—

A

Email Security

DMARC: quarantine

PASS

DMARC: quarantine

DMARC policy is quarantine — good protection

DMARC

Policy quarantine — good protection Record v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@wefunder.com,mailto:re+5bea8efad000@inbound.dmarcdigests.com; ruf=mailto:dmarc+forensicreports@wefunder.com; fo=1;

A+

Permissions-Policy

18 directives, 0 missing

PASS

18 directives, 0 missing

accelerometer=() — blocked for all origins

browsing-topics=() — blocked for all origins

camera=() — blocked for all origins

clipboard-read=() — blocked for all origins

clipboard-write=() — blocked for all origins

geolocation=() — blocked for all origins

gyroscope=() — blocked for all origins

hid=() — blocked for all origins

interest-cohort=() — blocked for all origins

magnetometer=() — blocked for all origins

microphone=() — blocked for all origins

payment=() — blocked for all origins

publickey-credentials-get=() — blocked for all origins

screen-wake-lock=() — blocked for all origins

serial=() — blocked for all origins

sync-xhr=() — blocked for all origins

usb=() — blocked for all origins

xr-spatial-tracking=(self)

Raw Header

accelerometer=() browsing-topics=() camera=() clipboard-read=() clipboard-write=() geolocation=() gyroscope=() hid=() interest-cohort=() magnetometer=() microphone=() payment=() publickey-credentials-get=() screen-wake-lock=() serial=() sync-xhr=() usb=() xr-spatial-tracking=(self)

Feature Permissions

Blocked Self Only Unrestricted Not Set

accelerometer Blocked

browsing-topics Blocked

camera Blocked

clipboard-read Blocked

clipboard-write Blocked

geolocation Blocked

gyroscope Blocked

hid Blocked

interest-cohort Blocked

magnetometer Blocked

microphone Blocked

payment Blocked

publickey-credentials-get Blocked

screen-wake-lock Blocked

serial Blocked

sync-xhr Blocked

usb Blocked

xr-spatial-tracking Self Only

A+

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) supported

The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.

HSTS enabled (base policy)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

TLS 1.3 in use (fastest handshake, 1-RTT)