Is cohere.com safe to use as a vendor?

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

What TLS version does cohere.com use?

cohere.com 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 cohere.com have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:spf-00852501.pphosted.com include:spf.pro...

Does cohere.com have security headers configured?

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

Does cohere.com use HSTS?

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

Has cohere.com been involved in a data breach?

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

Does cohere.com 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 cohere.com's SSL certificate valid?

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

cohere.com Security Report — Grade B- (80/100)

Q: Does cohere.com have DMARC configured?

Yes. cohere.com'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: 6/10 (within limit); DKIM configured (selectors: google, s1, s2). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Q: Does cohere.com have DNSSEC enabled?

No. Strengths: 2 nameservers configured (konnor.ns.cloudflare.com, davina.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 7 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 (cloudflare.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 cohere.com compares with the other 49 →

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 Configuration

TLS Protocol Support

HSTS Header

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 2–5 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-

cohere.com

80/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

7 items need attention

8 passed

Add missing cookie security settings

Cookie Security

1–2 hours High

This makes it meaningfully easier for an attacker to hijack authenticated customer sessions, increasing account-takeover risk. On cohere.com, most cookies are missing key protections: 1 cookie(s) can be sent over an unencrypted connection (missing the "Secure" flag); 1 cookie(s) can be read by page scripts, including malicious ones (missing "HttpOnly").

OWASP ASVS3.4

Session cookies use Secure, HttpOnly, and SameSite attributes

How to fix this

1Add Secure to every cookie your site sets — this is usually one line in your app's session/cookie config, not a DNS or hosting setting.

2Add HttpOnly to login/session cookies — same place as above, in your app's cookie settings.

3This needs a developer — it's a one-line change per cookie in your website's code, not something changeable from a hosting dashboard.

4Re-scan afterward to confirm all three flags are now set.

Cookie security guide

Report unlocked.

View all 8 passed checks

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

HSTS Header

CVE Exposure

Subprocessors & Tech Stack

Known Breaches

Certificate Hygiene

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

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded B

791 companies · LynxRadar ranking

Blocking Issues

Fail

Strengths: 1 cookie(s) analyzed; All cookies have SameSite attribute. Issues: 1/1 cookie(s) missing Secure flag (NEXT_LOCALE); 1/1 cookie(s) missing HttpOnly flag (NEXT_LOCALE).

Likelihood: ★★★★☆

Impact: ★★★★☆

2/5 present

Missing: CSP, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

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: 6/10 (within limit); DKIM configured (selectors: google, s1, s2). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

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: 2 nameservers configured (konnor.ns.cloudflare.com, davina.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 7 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 (cloudflare.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: ★☆☆☆☆

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: ★☆☆☆☆