Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
casetext.com scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, Known Breaches, TLS Configuration all passed.
2 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 casetext.com compares
Grade distribution across 2378 companies we've scanned. casetext.com scores better than 89% 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
casetext.com — Grade A- (90/100)
2378 companies scanned
Security checks
Each check inspects a different part of casetext.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
Certificate Hygiene
Strengths: Certificate valid, 86 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (daisy.ns.cloudflare.com., isaac.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 reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: s1).
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
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
2 items
Steps to improve casetext.com's security grade, ranked by impact.
1
Add optional security headers (Referrer-Policy, Permissions-Policy)
casetext.com has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://casetext.com | 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
Review certificate configuration
Certificate issues found for casetext.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_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: s1).
SPF Record
Present
v=spf1 include:_spf.casetext_com._d.easydmarc.pro ~all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 86 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (daisy.ns.cloudflare.com., isaac.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.