Is read.ai safe to use as a vendor?

read.ai scored 80/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 5 warnings, 1 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does read.ai use?

read.ai uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does read.ai have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:mail.zendesk.com include:spf.mandrillapp....

Does read.ai have security headers configured?

read.ai has 2 of 5 recommended security headers. Present: CSP, X-Frame-Options. Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy.

Does read.ai use HSTS?

Yes. HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.

Has read.ai been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does read.ai have known CVE vulnerabilities?

Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

Is read.ai's SSL certificate valid?

Yes. Strengths: Certificate valid, 83 days remaining; Issued by Google Trust Services.

read.ai Security Report — Grade B- (80/100)

Q: Does read.ai have DMARC configured?

Yes. read.ai's DMARC policy is set to 'quarantine'. SPF record: yes. Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 4/10 (within limit); DKIM configured (selectors: google, s1, s2, mandrill, zendesk1, zendesk2). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Q: Does read.ai have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-1739.awsdns-25.co.uk, ns-731.awsdns-27.net, ns-1395.awsdns-46.org, ns-168.awsdns-21.com); NS records span 4 providers (co.uk, awsdns-27.net, awsdns-46.org, awsdns-21.com) — genuine redundancy; SOA record present and MNAME consistent with NS set; 5 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

B-

Trust rating

Good · 80/100

Procurement snapshot

0 critical findings identified — these point to architectural gaps, not just configuration tweaks.

Strengths

MX Records & Mail Provider

TLS Protocol Support

TLS Configuration

HSTS Header

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 1–2 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned August 19, 2026

Score

100 75 50 25 0

B-

read.ai

80/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Pro subscribers only

ISO 27001

Certificate not on file

3rd party · accredited body

Pro subscribers only

GDPR

DPA not on file

Self-reported

Pro subscribers only

CCPA

Self-reported

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

6 items need attention

9 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for read.ai is partly set up, but there are gaps: . Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST CSFPR.AC-7

Email authentication is a required access control

How to fix this

1Double-check it's live: search "dmarc record checker" and enter read.ai.

Email authentication guide

Report unlocked.

View all 9 passed checks

MX Records & Mail Provider

TLS Protocol Support

TLS Configuration

HSTS Header

Known Breaches

Cookie Security

Subprocessors & Tech Stack

CVE Exposure

Certificate Hygiene

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.read.ai ↗

Security page

read.ai/security ↗

read.ai/privacy ↗

DPA (Data Processing Agreement)

read.ai/dpa ↗

Updated recently

Subprocessors List

read.ai/policies/subprocessors ↗

Similar companies

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Blocking Issues

2/5 present

Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

p=quarantine

Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 4/10 (within limit); DKIM configured (selectors: google, s1, s2, mandrill, zendesk1, zendesk2). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 4 nameservers configured (ns-1739.awsdns-25.co.uk, ns-731.awsdns-27.net, ns-1395.awsdns-46.org, ns-168.awsdns-21.com); NS records span 4 providers (co.uk, awsdns-27.net, awsdns-46.org, awsdns-21.com) — genuine redundancy; SOA record present and MNAME consistent with NS set; 5 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆