Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
healthsherpa.com scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, DNS Configuration, TLS Configuration all passed.
1 action item 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 healthsherpa.com compares
Grade distribution across 2378 companies we've scanned. healthsherpa.com scores better than 96% 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
healthsherpa.com — Grade A (95/100)
2378 companies scanned
Security checks
Each check inspects a different part of healthsherpa.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Certificate Hygiene
Strengths: Certificate valid, 246 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns4.dnsimple-edge.org., ns1.dnsimple.com., ns2.dnsimple-edge.net., ns3.dnsimple.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-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).
HSTS Header
HSTS enabled: max-age=631138519. Missing includeSubDomains. Missing preload directive.
Security Headers
4/5 security headers present. Missing: CSP.
CVE Exposure
Detected technologies: Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Recommended actions
1 item
Steps to improve healthsherpa.com's security grade, ranked by impact.
1
Review certificate configuration
Certificate issues found for healthsherpa.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
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_128_GCM_SHA256 (128-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).
SPF Record
Present
v=spf1 include:_spf.google.com include:servers.mcsv.net include:emsd1.com include:amazonses.com incl
Security Headers
4/5 present
Missing: CSP
HSTS
Enabled
HSTS enabled: max-age=631138519. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 246 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns4.dnsimple-edge.org., ns1.dnsimple.com., ns2.dnsimple-edge.net., ns3.dnsimple.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.