Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
bayesimpact.org scored 78/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.
3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How bayesimpact.org compares
Grade distribution across 2378 companies we've scanned. bayesimpact.org scores better than 59% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
bayesimpact.org — Grade C+ (78/100)
2378 companies scanned
Security checks
Each check inspects a different part of bayesimpact.org's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 2/5 security headers present. Missing: CSP, X-Content-Type-Options, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
HSTS Header
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
DMARC / Email Security
Strengths: DKIM configured (selectors: google, zendesk1, zendesk2). Issues: DMARC policy is 'none' (monitoring only, no enforcement); SPF record uses neutral (?all) — no real enforcement.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-d1.googledomains.com., ns-cloud-d3.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d4.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Certificate Hygiene
Strengths: Certificate valid, 71 days remaining; Issued by Let's Encrypt.
Recommended actions
3 items
Steps to improve bayesimpact.org's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Content-Type-Options, Permissions-Policy)
3 of 5 recommended security headers are missing on bayesimpact.org: CSP, X-Content-Type-Options, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Content-Type-Options: nosniff
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://bayesimpact.org | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Strengthen email authentication configuration
Email authentication is partially configured for bayesimpact.org but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.bayesimpact.org
3
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://bayesimpact.org | grep -i strict
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=none
Strengths: DKIM configured (selectors: google, zendesk1, zendesk2). Issues: DMARC policy is 'none' (monitoring only, no enforcement); SPF record uses neutral (?all) — no real enforcement.
SPF Record
Present
v=spf1 include:mail.zendesk.com include:spf.mailjet.com include:_spf.google.com ?all
Security Headers
2/5 present
Missing: CSP, X-Content-Type-Options, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Valid
Strengths: Certificate valid, 71 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-d1.googledomains.com., ns-cloud-d3.googledomains.com., ns-cloud-d2.googledomains.com., ns-cloud-d4.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.