Is brainkey.ai safe to use as a vendor?

brainkey.ai scored 71/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 6 checks passed, 2 warnings, 2 critical issues across 10 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does brainkey.ai use?

brainkey.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 brainkey.ai have SPF configured?

Yes. SPF record: v=spf1 include:_spf.google.com include:mailgun.org ~all

Does brainkey.ai have security headers configured?

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

Has brainkey.ai been involved in a data breach?

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

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

Yes. Strengths: Certificate valid, 59 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.

brainkey.ai Security Report — Grade C- (71/100)

Q: Does brainkey.ai have DMARC configured?

Yes. brainkey.ai's DMARC policy is set to 'quarantine'. SPF record: yes. Strengths: DMARC policy set to quarantine; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; DMARC pct=50 — policy only applies to 50% of mail; 50% of spoofed messages bypass enforcement.

Q: Does brainkey.ai use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Q: Does brainkey.ai have DNSSEC enabled?

No. Strengths: 2 nameservers configured (carlos.ns.cloudflare.com., ophelia.ns.cloudflare.com.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

C-

Trust rating

Fair · 71/100

Procurement snapshot

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

Strengths

TLS Configuration

Known Breaches

MX Records & Mail Provider

CVE Exposure

Questions to ask

Confirm DNSSEC rollout timeline

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 February 18, 2026

Your rating Industry average

Score

100 75 50 25 0

C-

brainkey.ai

71/100

Compliance & Certifications

Not yet verified

HIPAA

BAA not on file

Self-reported

HITRUST

Certificate not on file

3rd party

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Incident History

No public breaches on record

Security Posture

4 items need attention

6 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

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

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Remove "pct=50" from your DMARC record in your DNS settings (you're using Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim) so the policy covers all mail. Your current record with just that change:

v=DMARC1; p=quarantine; rua=mailto:[email protected]

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

Email authentication guide

Report unlocked.

View all 6 passed checks

TLS Configuration

Known Breaches

MX Records & Mail Provider

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Vanta Trust Center

trust.brainkey.ai/

DPA (Data Processing Agreement)

Subprocessors List

Tech Stack Detected

Subprocessors

Cloudflare

Similar companies in Healthcare / Health Tech

Appears in

Healthcare / Health Tech vendors

138 companies scanned by LynxRadar

Vendors graded C

699 companies · LynxRadar ranking

Blocking Issues

Not enabled

Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Likelihood: ★★★☆☆

Impact: ★★★★☆

0/5 present

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

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

p=quarantine

Strengths: DMARC policy set to quarantine; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; DMARC pct=50 — policy only applies to 50% of mail; 50% of spoofed messages bypass enforcement.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Not enabled

Strengths: 2 nameservers configured (carlos.ns.cloudflare.com., ophelia.ns.cloudflare.com.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆