Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=static.bienparabien.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
April 22, 2025
Valid Until
May 21, 2026
171 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
77:19:9F:99:6E:88:6F:27:08:9C:B7:C4:10:CA:4E:90:A8:46:DA:69:71:59:9A:E2:38:8B:A4:F2:B0:4D:DC:81
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=31536000
Content-Security-Policy
Good
default-src; img-src; style-src; +3 more
default-src 'self' data:; img-src 'self' static.bienparabien.com cdn.example.com s3.amazonaws.com xami.codster.io data:; style-src 'self' 'unsafe-inline'; script-src 'self' xami.codster.io; frame-src 'self'; connect-src 'self' static.bienparabien.com data:;
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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