F
Fail · 45/100
Shows significant security gaps that need urgent attention. Positive signals: Known Breaches, MX Records & Mail Provider, and CVE Exposure all passed. 4 action items identified, including 1 critical. The issues point to real architectural gaps, not just configuration tweaks. A focused remediation effort of 2–5 days could address all findings.
Trust Score Trend
→ No change
1 scan · Last scanned February 18, 2026
Score
100
75
50
25
0
F
45/100
Compliance & Certifications
SOC 2 Type II
3rd party · AICPA
Pro subscribers only
ISO 27001
3rd party · accredited body
Pro subscribers only
GDPR
Self-reported
Pro subscribers only
CCPA
Self-reported
Pro subscribers only
Incident History
None in 12 months
March 2026
ChatGPT data exposure
1 source
Pro subscribers only
April 2023 – Feb 2026
ChatGPT data exposure
1 source
Pro subscribers only
Security Posture
4 items need attention
3 passed
0 of 1 fixed
All 1 critical issue marked as fixed
Re-scan to confirm and update your score.
Turn off unknown — it's outdated and unsafe
TLS Configuration
This exposes traffic to interception or tampering using publicly documented weaknesses. preclus.io still accepts connections using unknown, an old encryption standard that attackers can exploit to read or tamper with traffic. Every major compliance framework (PCI-DSS, HIPAA, NIST) treats this as a failure. The fix is to simply stop offering it — modern browsers already use TLS 1.2/1.3 automatically, so real visitors won't notice the change.
PCI-DSS 4.0Req 4.2.1
Strong cryptography for transmission
NIST 800-52r2§3.4
TLS 1.0/1.1 must not be used
HIPAA§164.312(e)
Transmission security
How to fix this
1If you're on a managed host or CDN, set the minimum TLS version to 1.2, disabling the old unsafe versions in one click — usually a toggle in their dashboard's SSL/TLS settings. If you manage your own server, update the TLS settings in its config (nginx: ssl_protocols TLSv1.2 TLSv1.3).
ssl_protocols TLSv1.2 TLSv1.3;
2Confirm it worked: search "ssl checker" and enter preclus.io — TLS 1.0 and 1.1 should show as not supported.
Report unlocked.
View all 3 passed checks
Known Breaches
MX Records & Mail Provider
CVE Exposure
Company Signals
Claim profile →
Operational risk
Low
11 yrs operating. Well-funded
Lynxradar · Composite signal
Last funding
$40B
Series F · Mar 2025 · SoftBank-led
Crunchbase ↗
Employees
~3,000
+40% YoY growth
LinkedIn ↗
Trust Resources
Claim profile →
Trust Center
trust.preclus.io ↗
Security page
preclus.io/security ↗
Privacy Policy
preclus.io/privacy ↗
DPA (Data Processing Agreement)
preclus.io/dpa ↗
Updated recently
Subprocessors List
preclus.io/policies/subprocessors ↗
Similar companies
Appears in
Claim profile →
SOC 2 Type II certified vendors
847 companies · Updated weekly by LynxRadar
ISO 27001 certified SaaS
312 companies · Updated weekly by LynxRadar
Top AI vendors by trust score
94 companies · LynxRadar ranking
Enterprise-ready SaaS · Trust score A or above
203 companies · LynxRadar ranking
