Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
CN=staging-saraya-totalhealth.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
January 27, 2025
Valid Until
February 25, 2026
91 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
CA:9E:99:0A:C4:69:32:87:73:D8:3B:90:4A:98:8B:B9:5C:5E:C7:2E:C4:8E:01:A6:C0:24:0A:D0:49:A2:0F:41
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=63072000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; img-src; connect-src; +3 more
default-src 'self';img-src 'self' data: http: https: blob:;connect-src *;style-src 'self' 'unsafe-inline';script-src 'self' https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ 'unsafe-inline'; frame-src 'self' https://www.google.com/recaptcha/
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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