Is harvey.ai safe to use as a vendor?

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

What TLS version does harvey.ai use?

harvey.ai uses TLSv1.3 with TLS_AES_128_GCM_SHA256. TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does harvey.ai have DMARC configured?

Yes. harvey.ai's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 4/10 (within limit); DKIM configured (selectors: google).

Does harvey.ai have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:_spf.salesforce.com include:spf.protectio...

Does harvey.ai have security headers configured?

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

Does harvey.ai use HSTS?

Yes. HSTS enabled: max-age=63072000s (730 days). includeSubDomains present. Missing preload directive.

Has harvey.ai been involved in a data breach?

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

Does harvey.ai have known CVE vulnerabilities?

Detected technologies: Vercel, Next.js. (Vercel detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).

Is harvey.ai's SSL certificate valid?

Yes. Strengths: Certificate valid, 53 days remaining; Issued by Let's Encrypt.

harvey.ai Security Report — Grade B+ (88/100)

Q: Does harvey.ai have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com); 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: All nameservers are from a single provider (googledomains.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Featured in our Forbes AI 50 security study: see how harvey.ai compares with the other 49 →

B+

Trust rating

Good · 88/100

Procurement snapshot

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

Strengths

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

HSTS Header

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 1–4 days

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

Trust Score Trend

→ No change 1 scan · Last scanned September 28, 2026

Score

100 75 50 25 0

B+

harvey.ai

88/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

4 items need attention

11 passed

Add 4 missing security headers

Security Headers

1–2 hours High

This leaves visitors exposed to attacks like clickjacking and content-type sniffing. harvey.ai is missing 4 of the 5 security headers browsers use to protect visitors — for example, one stops your site being loaded inside a hidden frame on another site to trick people into clicking things (clickjacking). These are settings, not code changes, so they're usually quick to add. On top of that, 3 of the headers you do have are misconfigured: CSP: 'unsafe-inline' in script directives — negates XSS protection; CSP: 'unsafe-eval' allows eval() — weakens XSS protection; CSP: wildcard (*) source — any origin permitted.

PCI-DSS 4.0Req 6.4.1

Security headers are required application controls

OWASPSecure Headers

Recommended baseline for web applications

How to fix this

1Add these headers exactly as shown. You're using Vercel in front of this site — add it there, see https://vercel.com/docs/headers/response-headers.

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

Referrer-Policy: strict-origin-when-cross-origin

Permissions-Policy: camera=(), microphone=(), geolocation=()

2Fix these existing headers — they're present but not doing their job: CSP: 'unsafe-inline' in script directives — negates XSS protection; CSP: 'unsafe-eval' allows eval() — weakens XSS protection; CSP: wildcard (*) source — any origin permitted. You're using Vercel in front of this site — add it there, see https://vercel.com/docs/headers/response-headers.

3Confirm it worked: search "http header checker" and enter harvey.ai — the headers above should appear in the response.

Security headers guide

Report unlocked.

View all 11 passed checks

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

HSTS Header

Cookie Security

security.txt (RFC 9116)

CVE Exposure

Subprocessors & Tech Stack

Known Breaches

Certificate Hygiene

DMARC / Email Security

Couldn't check: Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so this isn't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

Security contact (security.txt)

harvey.ai/.well-known/security.txt

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded B

791 companies · LynxRadar ranking

Blocking Issues

1/5 present

Missing: X-Content-Type-Options, X-Frame-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: ★★★☆☆

Not enabled

Strengths: 4 nameservers configured (ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com); 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: All nameservers are from a single provider (googledomains.com) — a provider outage takes down the domain; 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: ★☆☆☆☆