Is threshold.network safe to use as a vendor?

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

What TLS version does threshold.network use?

threshold.network 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 threshold.network have SPF configured?

Yes. SPF record: v=spf1 include:_spf.google.com -all

Does threshold.network have security headers configured?

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

Does threshold.network use HSTS?

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

Has threshold.network been involved in a data breach?

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

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

Yes. Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services.

Does threshold.network have DNSSEC enabled?

Yes. Strengths: 2 nameservers configured (vick.ns.cloudflare.com., nora.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.

threshold.network Security Report — Grade B- (82/100)

Q: Does threshold.network have DMARC configured?

Yes. threshold.network's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit). Issues: DMARC policy is 'none' (monitoring only, no enforcement). Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

B-

Trust rating

Good · 82/100

Procurement snapshot

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

Strengths

Known Breaches

DNS Configuration

TLS Configuration

MX Records & Mail Provider

Estimated remediation effort: 3–6 hours

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-

threshold.network

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

Incident History

No public breaches on record

Security Posture

2 items need attention

8 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 threshold.network 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]

2If DKIM signing isn't on yet (we can't confirm it from outside): Turn on DKIM signing in Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim for the exact steps. It gives you a record to add in your DNS settings (you're using Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim).

3Double-check it's live: search "dmarc record checker" and enter threshold.network.

Email authentication guide

Report unlocked.

View all 8 passed checks

Known Breaches

DNS Configuration

TLS Configuration

MX Records & Mail Provider

HSTS Header

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

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

826 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 hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit). Issues: DMARC policy is 'none' (monitoring only, no enforcement). Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

Likelihood: ★★★☆☆

Impact: ★★★☆☆