Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
cash.app scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Cookie Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.
2 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How cash.app compares
Grade distribution across 2497 companies we've scanned. cash.app scores better than 92% of them.
78
A+
25
A
183
A-
190
B+
72
B
347
B-
120
C+
116
C
319
C-
116
D+
94
D
237
D-
600
F
cash.app — Grade A- (92/100)
2497 companies scanned
Security checks
Each check inspects a different part of cash.app's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
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).
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 4 nameservers configured (ns-1248.awsdns-28.org., ns-1816.awsdns-35.co.uk., ns-311.awsdns-38.com., ns-810.awsdns-37.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
HSTS Header
HSTS enabled: max-age=631152000s (7305 days) with includeSubDomains and preload. Meets best-practice configuration.
security.txt (RFC 9116)
Strengths: security.txt found with 2 field(s); Contact: https://bugcrowd.com/cashapp. Issues: security.txt expired 96 days ago (2026-01-01T00:00:00.000Z); Not PGP signed (recommended for authenticity).
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, zendesk1, zendesk2).
CVE Exposure
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.
Certificate Hygiene
Strengths: Certificate valid, 63 days remaining; Issued by Google Trust Services.
Recommended actions
2 items
Steps to improve cash.app's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for cash.app can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .app TLD
4
Verify: dig +dnssec cash.app
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (Referrer-Policy, Permissions-Policy)
cash.app has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://cash.app | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, zendesk1, zendesk2).
SPF Record
Present
v=spf1 include:cash.app._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=631152000s (7305 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 63 days remaining; Issued by Google Trust Services.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1248.awsdns-28.org., ns-1816.awsdns-35.co.uk., ns-311.awsdns-38.com., ns-810.awsdns-37.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.