Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
caremessage.org scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: DNS Configuration, Known Breaches, TLS Configuration 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 caremessage.org compares
Grade distribution across 2378 companies we've scanned. caremessage.org scores better than 64% 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
caremessage.org — Grade B- (80/100)
2378 companies scanned
Security checks
Each check inspects a different part of caremessage.org's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Security Headers
3/5 security headers present. Missing: CSP, X-Frame-Options.
Certificate Hygiene
Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (ned.ns.cloudflare.com., erin.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, k1, mandrill, smtpapi).
CVE Exposure
Detected technologies: Flywheel/5.1.0. No high or critical CVEs found for detected versions.
Recommended actions
3 items
Steps to improve caremessage.org's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on caremessage.org. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://caremessage.org | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (CSP, X-Frame-Options)
caremessage.org has most security headers configured. Missing: CSP, X-Frame-Options. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Verify with: curl -sI https://caremessage.org | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review certificate configuration
Certificate issues found for caremessage.org: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, k1, mandrill, smtpapi).
SPF Record
Present
v=spf1 include:_spf.google.com include:_spf.mailgun.org include:spf.tipalti.com include:23308455.sp
Security Headers
3/5 present
Missing: CSP, X-Frame-Options
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Issues
Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (ned.ns.cloudflare.com., erin.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.