Is upsolve.org safe to use as a vendor?

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

What TLS version does upsolve.org use?

upsolve.org 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 upsolve.org have SPF configured?

Yes. SPF record: v=spf1 include:mailgun.org ~all

Does upsolve.org have security headers configured?

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

Has upsolve.org been involved in a data breach?

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

Does upsolve.org have known CVE vulnerabilities?

Detected technologies: AmazonS3, Proxy/CDN, Gatsby/2.32.0. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No high or critical CVEs found for detected versions.

Is upsolve.org's SSL certificate valid?

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

upsolve.org Security Report — Grade C- (71/100)

Q: Does upsolve.org have DMARC configured?

Yes. upsolve.org's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; SPF soft-fail (~all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: google, k1, krs, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua) — policy violations won't be reported; Multiple SPF records found (4) — RFC 7208 requires exactly one. Behaviour is undefined and some receivers will reject mail outright.

Q: Does upsolve.org use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Q: Does upsolve.org have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-298.awsdns-37.com., ns-819.awsdns-38.net., ns-1265.awsdns-30.org., ns-1797.awsdns-32.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

C-

Trust rating

Fair · 71/100

Procurement snapshot

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

Strengths

Known Breaches

TLS Configuration

MX Records & Mail Provider

CVE Exposure

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

C-

upsolve.org

71/100

Compliance & Certifications

Not yet verified

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

4 items need attention

6 passed

Turn on HSTS (forces browsers to always use HTTPS)

HSTS Header

< 1 hour High

This puts visitor logins and session data at risk of interception on untrusted networks. upsolve.org doesn't send the HSTS header, so a browser can still be tricked into connecting over plain, unencrypted HTTP instead of HTTPS — an attacker on the same network (e.g. public wifi) can exploit that gap to intercept traffic. Turning HSTS on tells every browser "always use HTTPS for this site, no exceptions."

PCI-DSS 4.0Req 6.4.1

Required application security controls

NIST 800-53SC-8

Transmission confidentiality and integrity

How to fix this

1Add this response header to your site. You're using Amazon CloudFront in front of this site — add it there, see https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/creating-response-headers-policies.html.

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2Before adding it, make sure every subdomain (not just the main site) also works over HTTPS — HSTS applies site-wide.

3Confirm it's live: search "http header checker" and enter upsolve.org.

4Once confirmed, submit the domain at hstspreload.org so browsers enforce HTTPS even on a user's very first visit.

HSTS guide

Report unlocked.

View all 6 passed checks

Known Breaches

TLS Configuration

MX Records & Mail Provider

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

Amazon CloudFront

Similar companies in Nonprofit

Appears in

Nonprofit vendors

22 companies scanned by LynxRadar

Vendors graded C

699 companies · LynxRadar ranking

Blocking Issues

Not enabled

Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Likelihood: ★★★☆☆

Impact: ★★★★☆

0/5 present

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

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

p=none

Strengths: DMARC pct=100 — policy applies to all mail; SPF soft-fail (~all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: google, k1, krs, smtpapi). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua) — policy violations won't be reported; Multiple SPF records found (4) — RFC 7208 requires exactly one. Behaviour is undefined and some receivers will reject mail outright.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Not enabled

Strengths: 4 nameservers configured (ns-298.awsdns-37.com., ns-819.awsdns-38.net., ns-1265.awsdns-30.org., ns-1797.awsdns-32.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆