Open
Cached
·
just now
81/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
PayPal
Amazon S3
Braintree
Cloudflare CDNJS
Cloudflare Web Analytics
Dropbox
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Optimize
Google Search
Google Static File Front End
Google Tag Manager
Iframely
JW Player
Mailchimp
Stripe
TikTok Analytics
Twitter
unpkg
YouTube
Google Cloud
Certificate Information
Subject
CN=maxspreadsheet.com
Issuer
C=US, O=Let's Encrypt, CN=YR2
Valid From
June 15, 2026
Valid Until
September 13, 2026
39 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B8:8B:17:07:E8:4B:B4:7B:35:72:C0:4F:0E:1E:A8:9F:87:BF:7A:6C:AC:0B:33:9A:EC:32:81:FA:B6:D2:8B:7C
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
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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