Is reflection.ai safe to use as a vendor?

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

What TLS version does reflection.ai use?

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

Yes. reflection.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 soft-fail (~all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: google, s1, s2).

Does reflection.ai have SPF configured?

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

Does reflection.ai have security headers configured?

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

Does reflection.ai use HSTS?

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

Has reflection.ai been involved in a data breach?

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

Does reflection.ai have known CVE vulnerabilities?

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

Is reflection.ai's SSL certificate valid?

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

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

Q: Does reflection.ai have DNSSEC enabled?

No. Strengths: 2 nameservers configured (dane.ns.cloudflare.com, courtney.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: 3 A record(s), 3 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 reflection.ai compares with the other 49 →

A-

Trust rating

Excellent · 92/100

Procurement snapshot

No critical findings. The 5 remaining items are configuration gaps, not architectural problems.

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

A-

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

Protect incoming email from downgrade attacks (MTA-STS)

MTA-STS & TLS Reporting

2–4 hours Medium

This allows inbound email to be silently downgraded and intercepted without warning. This is a more advanced setting — skip it if you're not sure, and come back once the items above are handled. reflection.ai has no MTA-STS policy, which means an attacker positioned on the network path could silently downgrade incoming email from encrypted to unencrypted, with no warning to either side.

How to fix this

1This one usually needs a developer or your hosting provider's support team — it involves publishing a small text file on your website, not just a DNS record.

v=STSv1; id=20260101000000

version: STSv1 mode: testing mx: mail.reflection.ai max_age: 604800

2Add a TXT record with the name "_mta-sts" in your DNS settings (you're using Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim) (id= just needs to be any unique short code you make up, e.g. today's date), with this value:

3Host a small policy file at https://mta-sts.reflection.ai/.well-known/mta-sts.txt with the content below.

4Start in "testing" mode for a couple of weeks, check the reports, then switch to "enforce".

MTA-STS guide

Report unlocked.

View all 10 passed checks

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

HSTS Header

Cookie Security

Subprocessors & Tech Stack

Known Breaches

CVE Exposure

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

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

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 (dane.ns.cloudflare.com, courtney.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: 3 A record(s), 3 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: ★☆☆☆☆

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