Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
Afterpay
Bugsnag
Contentful
Datadog
Facebook
Fullstory
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
Loggly
OneTrust
Podscribe
Samplicio
SmartRecruiters
Square
Statuspage
Tapad
Vimeo
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=cash.app
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 12, 2026
Valid Until
June 10, 2026
34 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
CF:7E:B2:8C:D6:F2:0E:81:29:98:10:22:CD:E7:1D:D2:12:02:0B:30:7F:2A:86:AA:81:F9:D3:62:CA:12:01:FB
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Excellent
max-age=631152000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports