Is olymplabs.io safe to use as a vendor?

olymplabs.io scored 80/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 6 warnings, 0 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does olymplabs.io use?

olymplabs.io 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 olymplabs.io have SPF configured?

Yes. SPF record: v=spf1 include:_spf.protonmail.ch ~all

Does olymplabs.io have security headers configured?

olymplabs.io has 5 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. All recommended headers present.

Does olymplabs.io use HSTS?

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

Has olymplabs.io been involved in a data breach?

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

Does olymplabs.io have known CVE vulnerabilities?

Detected technologies: BunnyCDN-WA1-1431. (BunnyCDN-WA1-1431 detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

olymplabs.io Security Report — Grade B- (80/100)

Q: Does olymplabs.io have DMARC configured?

Yes. olymplabs.io's DMARC policy is set to 'quarantine'. SPF record: yes. Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 1/10 (within limit). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

Q: Is olymplabs.io's SSL certificate valid?

Issues detected. Strengths: Certificate valid, 32 days remaining; Issued by Actalis S.p.A.; 90 certificates logged in CT. Issues: Certificates issued by 5 different CAs (threshold: 3 for 90 logged certs) — possible misconfiguration or shadow IT.

Q: Does olymplabs.io have DNSSEC enabled?

No. Strengths: 2 nameservers configured (kiki.bunny.net, coco.bunny.net); SOA record present and MNAME consistent with NS set; 2 MX record(s) present; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (bunny.net) — a provider outage takes down the domain.

B-

Trust rating

Good · 80/100

Procurement snapshot

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

Strengths

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

DNS CAA Records

Questions to ask

Confirm DNSSEC rollout timeline

Estimated remediation effort: 1–2 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned August 16, 2026

Score

100 75 50 25 0

B-

olymplabs.io

80/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Pro subscribers only

ISO 27001

Certificate not on file

3rd party · accredited body

Pro subscribers only

GDPR

DPA not on file

Self-reported

Pro subscribers only

CCPA

Self-reported

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

6 items need attention

9 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for olymplabs.io is partly set up, but there are gaps: DKIM isn't set up. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST CSFPR.AC-7

Email authentication is a required access control

How to fix this

1Turn on DKIM signing — look for "DKIM" under your email provider's admin/security settings. It will generate a record for you to paste into the same DNS settings above.

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

Email authentication guide

Report unlocked.

View all 9 passed checks

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

DNS CAA Records

HSTS Header

Cookie Security

Known Breaches

CVE Exposure

Subprocessors & Tech Stack

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.olymplabs.io ↗

Security page

olymplabs.io/security ↗

olymplabs.io/privacy ↗

DPA (Data Processing Agreement)

olymplabs.io/dpa ↗

Updated recently

Subprocessors List

olymplabs.io/policies/subprocessors ↗

Similar companies

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Medium Priority

Not enabled

Strengths: 2 nameservers configured (kiki.bunny.net, coco.bunny.net); SOA record present and MNAME consistent with NS set; 2 MX record(s) present; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: All nameservers are from a single provider (bunny.net) — a provider outage takes down the domain.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Warn

Strengths: MX patterns specified: mailsec.protonmail.ch, mail.protonmail.ch; 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: ★★★☆☆

p=quarantine

Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 1/10 (within limit). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Best Practice

5/5 present

All headers configured.

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

Issues

Strengths: Certificate valid, 32 days remaining; Issued by Actalis S.p.A.; 90 certificates logged in CT. Issues: Certificates issued by 5 different CAs (threshold: 3 for 90 logged certs) — possible misconfiguration or shadow IT.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆