Is alpaca.markets safe to use as a vendor?

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

What TLS version does alpaca.markets use?

alpaca.markets 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 alpaca.markets have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com in...

Does alpaca.markets have security headers configured?

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

Has alpaca.markets been involved in a data breach?

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

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

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

alpaca.markets Security Report — Grade C (76/100)

Q: Does alpaca.markets have DMARC configured?

Yes. alpaca.markets'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 hard-fail (-all) configured; SPF DNS lookup count: 4/10 (within limit); DKIM configured (selectors: google, s1, s2, zendesk1, zendesk2). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Q: Does alpaca.markets use HSTS?

Partially. HSTS present but max-age is low (15724800s). Recommended minimum: 15768000 (6 months).

Q: Does alpaca.markets have DNSSEC enabled?

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

Trust rating

Fair · 76/100

Procurement snapshot

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

Strengths

SOC 2 Type II

ISO 27001

GDPR

CSA STAR

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

alpaca.markets

76/100

Compliance & Certifications

4 of 4 verified via Trust Center

SOC 2 Type II

Listed on Vanta Trust Center

View trust center

ISO 27001

Listed on Vanta Trust Center

View trust center

GDPR

Listed on Vanta Trust Center

View trust center

CSA STAR

Listed on Vanta Trust Center

View trust center

Incident History

No public breaches on record

Security Posture

4 items need attention

6 passed

Add 5 missing security headers

Security Headers

1–2 hours High

This leaves visitors exposed to attacks like clickjacking and content-type sniffing. alpaca.markets is missing 5 of the 5 security headers browsers use to protect visitors — for example, one stops your site being loaded inside a hidden frame on another site to trick people into clicking things (clickjacking). These are settings, not code changes, so they're usually quick to add.

PCI-DSS 4.0Req 6.4.1

Security headers are required application controls

OWASPSecure Headers

Recommended baseline for web applications

How to fix this

1Add these headers exactly as shown. You're using Cloudflare in front of this site — add it there, see https://developers.cloudflare.com/rules/transform/response-header-modification/create-dashboard/.

Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

Referrer-Policy: strict-origin-when-cross-origin

Permissions-Policy: camera=(), microphone=(), geolocation=()

2Confirm it worked: search "http header checker" and enter alpaca.markets — the headers above should appear in the response.

Security headers 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.alpaca.markets

DPA (Data Processing Agreement)

Subprocessors List

Tech Stack Detected

Subprocessors

Cloudflare

Similar companies in B2B SaaS / Software

Appears in

B2B SaaS / Software vendors

770 companies scanned by LynxRadar

Vendors graded C

729 companies · LynxRadar ranking

Blocking Issues

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; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 4/10 (within limit); DKIM configured (selectors: google, s1, s2, zendesk1, zendesk2). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Not enabled

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

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

HSTS present but max-age is low (15724800s). Recommended minimum: 15768000 (6 months).

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆