Is orca.security safe to use as a vendor?

orca.security scored 98/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 1 warnings, 0 critical issues across 10 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does orca.security use?

orca.security 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 orca.security have DMARC configured?

Yes. orca.security'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; Forensic reports (ruf) configured; SPF DNS lookup count: 0/10 (within limit); DKIM configured (selectors: google, s1, s2, smtpapi).

Does orca.security have SPF configured?

Yes. SPF record: v=spf1 redirect=c97hdkch._spf._d.mim.ec

Does orca.security have security headers configured?

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

Does orca.security use HSTS?

Yes. HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.

Has orca.security been involved in a data breach?

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

Does orca.security have known CVE vulnerabilities?

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

Is orca.security's SSL certificate valid?

Yes. Strengths: Certificate valid, 184 days remaining; Issued by Sectigo Limited.

orca.security Security Report — Grade A+ (98/100)

Q: Is orca.security's SSL certificate valid?

Yes. Strengths: Certificate valid, 184 days remaining; Issued by Sectigo Limited.

Q: Does orca.security have DNSSEC enabled?

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

A+

Trust rating

Excellent · 98/100

Procurement snapshot

No critical findings. The 1 remaining item is a configuration gap, not an architectural problem.

Strengths

TLS Configuration

Known Breaches

DMARC / Email Security

MX Records & Mail Provider

Questions to ask

Confirm DNSSEC rollout timeline

Estimated remediation effort: 1–3 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 15, 2026

Score

100 75 50 25 0

A+

orca.security

98/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

1 item needs attention

9 passed

Turn on DNSSEC for your domain

DNS Configuration

1–3 days (mostly waiting, not active work) Medium

This allows an attacker to silently redirect your visitors to a fake site. DNSSEC is a signature system that stops attackers from forging DNS answers — without it, someone could redirect visitors of orca.security to a fake site without them noticing. Turning it on takes coordination between your DNS provider and your domain registrar, but it's a one-time setup.

NIST 800-53SC-20

Secure name/address resolution service

How to fix this

1Check whether your DNS provider supports DNSSEC in your DNS provider's dashboard (whichever company manages this domain's DNS — often your registrar, e.g. GoDaddy, Namecheap, or Cloudflare) — most major ones do (Cloudflare, Route53, GoDaddy, Namecheap).

2Turn on DNSSEC signing there — it will generate a DS record for you.

3Copy that DS record into your domain registrar's DNSSEC settings for the .security domain.

4Confirm it worked: search "dnssec checker" and enter orca.security.

DNSSEC guide

View all 9 passed checks

TLS Configuration

Known Breaches

DMARC / Email Security

MX Records & Mail Provider

HSTS Header

Security Headers

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

SafeBase Trust Center

trustcenter.orca.security

DPA (Data Processing Agreement)

Subprocessors List

Tech Stack Detected

Subprocessors

Cloudflare

Similar companies

Appears in

Vendors graded A

377 companies · LynxRadar ranking

Top 10% by security score

287 companies · LynxRadar ranking

Medium Priority

Not enabled

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

Likelihood: ★★☆☆☆

Impact: ★★★☆☆