Overview
Findings
Actions
Details
Related
LynxRadar → Directory → voyage.bio
F
40 / 100

voyage.bio

Security report · Scanned February 18, 2026

Checks
8
Passed
3
Warnings
1
Critical
1
AI-Generated Summary
What this means

voyage.bio scored 40/100 and does not meet the minimum security posture threshold. The most critical issue is: Set up email authentication (DMARC, SPF, DKIM). This must be addressed before the vendor can be approved for procurement or data processing activities.

Critical gaps in: DMARC / Email Security. Positive signals: DNS Configuration, Known Breaches, CVE Exposure all passed.

2 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

How voyage.bio compares

Grade distribution across 2378 companies we've scanned. voyage.bio scores better than 11% of them.

11th percentile
0 Percentile rank 100
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
voyage.bio — Grade F (40/100) 2378 companies scanned
Security checks

Each check inspects a different part of voyage.bio's public security setup. Green means healthy, yellow needs attention, red is a problem.

DMARC / Email Security
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Problem
Certificate Hygiene
Issues: Could not retrieve certificate details.
Needs work
TLS Configuration
Could not complete TLS handshake with voyage.bio:443 — [Errno 111] Connection refused
Skipped
HSTS Header
Could not fetch https://voyage.bio — connection failed or timed out.
Skipped
Security Headers
Could not fetch https://voyage.bio — connection failed or timed out.
Skipped
Known Breaches
No known breaches found in public disclosure databases.
Healthy
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Healthy
DNS Configuration
Strengths: 2 nameservers configured (ns18.ovh.net., dns18.ovh.net.); 3 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
Recommended actions
2 items

Steps to improve voyage.bio's security grade, ranked by impact.

1
Set up email authentication (DMARC, DKIM)
Impact: 1–2 Days
CRITICAL
Without email authentication, anyone can send emails that appear to come from voyage.bio. This is the most common vector for phishing attacks targeting employees and customers. DMARC, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
2
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for voyage.bio: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
At a glance

Key data points from the scan.

TLS Version
Issues detected
Could not complete TLS handshake with voyage.bio:443 — [Errno 111] Connection refused
DMARC Policy
Not configured
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 include:mx.ovh.com ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://voyage.bio — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Enabled
Strengths: 2 nameservers configured (ns18.ovh.net., dns18.ovh.net.); 3 MX records present; DNSSEC enabled; Zone transfers properly restricted.