Is cash.app safe to use as a vendor?

cash.app scored 82/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 5 warnings, 1 critical issues across 15 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does cash.app use?

cash.app 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 cash.app have DMARC configured?

Yes. cash.app'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; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google, zendesk1, zendesk2).

Does cash.app have SPF configured?

Yes. SPF record found: v=spf1 include:cash.app._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.v...

Does cash.app have security headers configured?

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

Does cash.app use HSTS?

Yes. HSTS enabled: max-age=631152000s (7305 days) with includeSubDomains and preload. Meets best-practice configuration.

Has cash.app been involved in a data breach?

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

Does cash.app 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.

cash.app Security Report — Grade B- (82/100)

Q: Is cash.app's SSL certificate valid?

Issues detected. Strengths: Certificate valid, 61 days remaining; Issued by Google Trust Services; 2564 certificates logged in CT. Issues: Certificates issued by 12 different CAs (threshold: 8 for 2564 logged certs) — possible misconfiguration or shadow IT.

Q: Does cash.app have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-1816.awsdns-35.co.uk, ns-311.awsdns-38.com, ns-810.awsdns-37.net, ns-1248.awsdns-28.org); NS records span 4 providers (co.uk, awsdns-38.com, awsdns-37.net, awsdns-28.org) — genuine redundancy; SOA record present and MNAME consistent with NS set; 5 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

B-

Trust rating

Good · 82/100

Procurement snapshot

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

Strengths

TLS Configuration

TLS Protocol Support

HSTS Header

security.txt (RFC 9116)

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 2–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 June 10, 2026

Your rating Industry average

Score

100 75 50 25 0

B-

cash.app

82/100

Compliance & Certifications

Not yet verified

PCI-DSS

AOC not on file

3rd party · QSA

SOC 2 Type II

Audit report not on file

3rd party · AICPA

DORA

Not on file

EU regulatory

Incident History

No public breaches on record

Security Posture

6 items need attention

9 passed

Add missing cookie security settings

Cookie Security

1–2 hours High

This makes it meaningfully easier for an attacker to hijack authenticated customer sessions, increasing account-takeover risk. On cash.app, most cookies are missing key protections: 1 cookie(s) can be read by page scripts, including malicious ones (missing "HttpOnly"); 3 cookie(s) don't restrict cross-site requests (missing "SameSite").

OWASP ASVS3.4

Session cookies use Secure, HttpOnly, and SameSite attributes

How to fix this

1Add HttpOnly to login/session cookies — same place as above, in your app's cookie settings.

2Add SameSite=Lax (or Strict for sensitive cookies) to every cookie.

3This needs a developer — it's a one-line change per cookie in your website's code, not something changeable from a hosting dashboard.

4Re-scan afterward to confirm all three flags are now set.

Cookie security guide

Report unlocked.

View all 9 passed checks

TLS Configuration

TLS Protocol Support

HSTS Header

security.txt (RFC 9116)

Known Breaches

DMARC / Email Security

MX Records & Mail Provider

CVE Exposure

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Self-hosted Trust Center

cash.app/security

Security contact (security.txt)

cash.app/.well-known/security.txt

DPA (Data Processing Agreement)

Subprocessors List

Tech Stack Detected

Subprocessors

SquareCloudflare

Similar companies in Fintech / Payments

Appears in

Fintech / Payments vendors

109 companies scanned by LynxRadar

Vendors graded B

794 companies · LynxRadar ranking

Blocking Issues

Fail

Strengths: 4 cookie(s) analyzed; All cookies have Secure flag. Issues: 1/4 cookie(s) missing HttpOnly flag (__atid); 3/4 cookie(s) missing SameSite attribute (__nsid, __st, __atid).

Likelihood: ★★★★☆

Impact: ★★★★☆

Medium Priority

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 4 nameservers configured (ns-1816.awsdns-35.co.uk, ns-311.awsdns-38.com, ns-810.awsdns-37.net, ns-1248.awsdns-28.org); NS records span 4 providers (co.uk, awsdns-38.com, awsdns-37.net, awsdns-28.org) — genuine redundancy; SOA record present and MNAME consistent with NS set; 5 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

3/5 present

Missing: Referrer-Policy, Permissions-Policy

Likelihood: ★★☆☆☆

Impact: ★☆☆☆☆

Issues

Strengths: Certificate valid, 61 days remaining; Issued by Google Trust Services; 2564 certificates logged in CT. Issues: Certificates issued by 12 different CAs (threshold: 8 for 2564 logged certs) — possible misconfiguration or shadow IT.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆