Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=*.lisk.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
December 23, 2025
Valid Until
January 21, 2027
374 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D7:84:A0:4E:B4:FF:02:6D:54:3D:8C:46:60:78:4D:1E:4B:26:DD:72:AB:DF:C0:FC:5A:C9:37:51:CD:B5:41:65
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=15768000
Content-Security-Policy
Basic
upgrade-insecure-requests; base-uri; object-src; +3 more
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-60BEkYoNNngJcR7yFaaJFvU8d' 'strict-dynamic'; frame-ancestors 'self'; manifest-src 'self'
X-Frame-Options
Good
SAMEORIGIN
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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