Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=ckfr.org
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
January 04, 2026
Valid Until
April 04, 2026
62 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
33:84:36:56:7F:56:C2:DD:35:99:67:E3:22:FD:61:77:62:29:DD:05:6F:0A:B0:C6:CF:7D:38:04:B4:35:DD:5D
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=63072000
Content-Security-Policy
Weak
upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin
Permissions-Policy
Present
geolocation ();midi ();sync-xhr ();microphone ();camera ();magnetometer ();gyroscope ();fullscreen (self);payment ();
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
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