Is fal.ai safe to use as a vendor?

fal.ai scored 88/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 fal.ai use?

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

Yes. fal.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: 3/10 (within limit); DKIM configured (selectors: google, s1, s2, k1, resend).

Does fal.ai have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:mg-spf.greenhouse.io include:_spf.salesfo...

Does fal.ai have security headers configured?

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

Does fal.ai use HSTS?

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

Has fal.ai been involved in a data breach?

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

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

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

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

Q: Does fal.ai have DNSSEC enabled?

No. Strengths: 2 nameservers configured (cody.ns.cloudflare.com, cecelia.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: 1 A record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain; DNSSEC partially configured: DNSKEY present at apex but DS record is absent from the parent zone — resolvers cannot validate signatures. Upload the DS record at your domain registrar to complete the chain of trust..

Featured in our Forbes AI 50 security study: see how fal.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

DMARC / Email Security

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: about 1 day

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+

fal.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

6 items need attention

9 passed

Finish turning on DNSSEC (one record left)

DNS Configuration

30 minutes High

DNS responses for this domain currently have no real protection against tampering. DNSSEC is half set up for fal.ai — the signing part is done, but one more record (called a "DS record") still needs to be copied over to your domain registrar to finish activating it. Until then, it provides no protection.

NIST 800-53SC-20

Secure name/address resolution service

How to fix this

1Log in to your domain registrar (the company you bought the domain from — not necessarily your DNS/website host).

2Find the "DNSSEC" or "DS records" section of the domain's settings.

3Go to your DNS provider's dashboard in your Cloudflare DNS dashboard (https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/), copy the DS record shown there, and paste it into the registrar.

4Confirm it worked: search "dnssec checker" and enter fal.ai.

DNSSEC guide

Report unlocked.

View all 9 passed checks

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

DMARC / Email Security

Certificate Hygiene

Known Breaches

CVE Exposure

HSTS Header

Subprocessors & Tech Stack

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

1/5 present

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

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

Not enabled

Strengths: 2 nameservers configured (cody.ns.cloudflare.com, cecelia.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: 1 A record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain; DNSSEC partially configured: DNSKEY present at apex but DS record is absent from the parent zone — resolvers cannot validate signatures. Upload the DS record at your domain registrar to complete the chain of trust..

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

Warn

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

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Best Practice

Warn

Strengths: CAA records configured at fal.ai (10 record(s)); Authorised CAs: letsencrypt.org, ssl.com, pki.goog; cansignhttpexchanges=yes, comodoca.com, digicert.com; cansignhttpexchanges=yes; Wildcard CAs: comodoca.com, ssl.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes. Issues: No iodef record — CA violations won't be reported to the domain owner.

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