Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
sapling.ai scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, TLS Configuration, HSTS Header 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 sapling.ai compares
Grade distribution across 2598 companies we've scanned. sapling.ai scores better than 96% of them.
83
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
sapling.ai — Grade A (95/100)
2598 companies scanned
Security checks
Each check inspects a different part of sapling.ai's public security setup. Green means healthy, yellow needs attention, red is a problem.
Certificate Hygiene
Strengths: Certificate valid, 375 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
DNS Configuration
Strengths: 4 nameservers configured (ns-853.awsdns-42.net., ns-1256.awsdns-29.org., ns-1547.awsdns-01.co.uk., ns-501.awsdns-62.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 hard-fail (-all); DKIM configured (selectors: google, k1, mandrill). Issues: DMARC has no aggregate report URI (rua).
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.
Recommended actions
1 item
Steps to improve sapling.ai's security grade, ranked by impact.
1
Review certificate configuration
Certificate issues found for sapling.ai: 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 hard-fail (-all); DKIM configured (selectors: google, k1, mandrill). Issues: DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 include:servers.mcsv.net include:spf.mandrillapp.com include:amazonses.com include:_spf.googl
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 375 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-853.awsdns-42.net., ns-1256.awsdns-29.org., ns-1547.awsdns-01.co.uk., ns-501.awsdns-62.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.