Is hive.co safe to use as a vendor?

hive.co scored 80/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 7 checks passed, 2 warnings, 1 critical issues across 10 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does hive.co use?

hive.co uses TLSv1.3 with TLS_AES_128_GCM_SHA256. TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does hive.co have SPF configured?

Yes. SPF record: v=spf1 include:_spf.google.com include:45134193.spf06.hubspotemail.net ~all

Does hive.co have security headers configured?

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

Does hive.co use HSTS?

Yes. HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.

Has hive.co been involved in a data breach?

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

Does hive.co have known CVE vulnerabilities?

Detected technologies: nginx/1.14.0. No high or critical CVEs found for detected versions.

Is hive.co's SSL certificate valid?

Yes. Strengths: Certificate valid, 298 days remaining; Issued by Amazon. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

hive.co Security Report — Grade B- (80/100)

Q: Does hive.co have DMARC configured?

Yes. hive.co's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Q: Does hive.co have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-1275.awsdns-31.org., ns-1567.awsdns-03.co.uk., ns-311.awsdns-38.com., ns-568.awsdns-07.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

B-

Trust rating

Good · 80/100

Procurement snapshot

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

Strengths

SOC 2 Type II

GDPR

Known Breaches

MX Records & Mail Provider

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

B-

hive.co

80/100

Compliance & Certifications

2 of 3 verified via Trust Center

SOC 2 Type II

Listed on self-hosted Trust Center

View trust center

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

Listed on self-hosted Trust Center

View trust center

Incident History

No public breaches on record

Security Posture

3 items need attention

7 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for hive.co is partly set up, but there are gaps: your DMARC policy is set to monitor-only, so nothing actually gets blocked yet. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Change your DMARC policy from "none" to "quarantine" in your DNS settings (you're using Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim) — this moves suspicious mail to spam instead of just watching it happen. Your current record with just that change:

v=DMARC1; p=quarantine; rua=mailto:[email protected]

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

Email authentication guide

Report unlocked.

View all 7 passed checks

Known Breaches

MX Records & Mail Provider

TLS Configuration

HSTS Header

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Self-hosted Trust Center

trust.hive.co/

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 B

794 companies · LynxRadar ranking

Blocking Issues

2/5 present

Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

p=none

Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Not enabled

Strengths: 4 nameservers configured (ns-1275.awsdns-31.org., ns-1567.awsdns-03.co.uk., ns-311.awsdns-38.com., ns-568.awsdns-07.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆