Is sierra.ai safe to use as a vendor?

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

What TLS version does sierra.ai use?

sierra.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 sierra.ai have DMARC configured?

Yes. sierra.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; SPF hard-fail (-all) configured; SPF DNS lookup count: 4/10 (within limit); DKIM configured (selectors: google, selector1).

Does sierra.ai have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:44905748.spf07.hubspotemail.net include:s...

Does sierra.ai have security headers configured?

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

Does sierra.ai use HSTS?

Yes. HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.

Has sierra.ai been involved in a data breach?

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

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

Yes. Strengths: Certificate valid, 81 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

sierra.ai Security Report — Grade A- (92/100)

Q: Does sierra.ai have DNSSEC enabled?

No. Strengths: 2 nameservers configured (paul.ns.cloudflare.com, candy.ns.cloudflare.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: 2 A record(s), 2 AAAA 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 sierra.ai compares with the other 49 →

A-

Trust rating

Excellent · 92/100

Procurement snapshot

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

Strengths

MX Records & Mail Provider

TLS Protocol Support

security.txt (RFC 9116)

TLS Configuration

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

A-

sierra.ai

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

5 items need attention

10 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 sierra.ai, most cookies are missing key protections: 1 cookie(s) can be sent over an unencrypted connection (missing the "Secure" flag); 2 cookie(s) can be read by page scripts, including malicious ones (missing "HttpOnly"); 1 cookie(s) don't restrict cross-site requests (missing "SameSite").

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.

3Add SameSite=Lax (or Strict for sensitive cookies) to every cookie.

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

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

Cookie security guide

Report unlocked.

View all 10 passed checks

MX Records & Mail Provider

TLS Protocol Support

security.txt (RFC 9116)

TLS Configuration

HSTS Header

Subprocessors & Tech Stack

CVE Exposure

Known Breaches

DMARC / Email Security

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

Security contact (security.txt)

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

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded A

377 companies · LynxRadar ranking

Top 10% by security score

287 companies · LynxRadar ranking

Blocking Issues

Fail

Strengths: 3 cookie(s) analyzed. Issues: 1/3 cookie(s) missing Secure flag (sai_show_locale_prompt); 2/3 cookie(s) missing HttpOnly flag (sai_country, sai_show_locale_prompt); 1/3 cookie(s) missing SameSite attribute (sai_show_locale_prompt).

Likelihood: ★★★★☆

Impact: ★★★★☆

Medium Priority

Warn

Strengths: MX patterns specified: aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com ...; All MX records are covered by policy MX patterns; Policy max_age: 7 days; SMTP TLS Reporting (TLSRPT) configured — delivery failures reported to: mailto:[email protected]. Issues: MTA-STS in testing mode — TLS failures are reported but not enforced; delivery is not protected.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 2 nameservers configured (paul.ns.cloudflare.com, candy.ns.cloudflare.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: 2 A record(s), 2 AAAA 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: ★☆☆☆☆

3/5 present

Missing: X-Frame-Options, Permissions-Policy

Likelihood: ★★☆☆☆

Impact: ★☆☆☆☆