Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Amplitude
Amazon S3
Bing
Cloudflare
Cloudflare CDN
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
jsDelivr
Microsoft Clarity
Plaid
Pusher
Statuspage
Stripe
Supabase
Active incidents
Tapfiliate
Vercel
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=app.faststatement.com
Issuer
C=US, O=Let's Encrypt, CN=YR1
Valid From
July 09, 2026
Valid Until
October 07, 2026
48 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E7:70:9A:A1:64:F1:46:67:35:A4:EE:28:CA:EE:0A:53:3C:36:FF:9C:5A:6C:81:E8:49:DA:01:EC:86:24:B4:6B
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
Present
max-age=63072000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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