Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=www.centauri.digital
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
January 11, 2026
Valid Until
April 11, 2026
86 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
3F:ED:E8:27:B6:BB:40:11:0A:AC:D4:80:29:81:68:DB:42:69:ED:81:C9:E1:0A:C5:47:7A:B7:89:79:69:FE:08
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
frame-ancestors; default-src; font-src; +1 more
frame-ancestors 'none'; default-src 'self'; font-src https://fonts.gstatic.com/ 'self'; style-src https://fonts.googleapis.com/ 'self';
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
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