Open
Cached
·
just now
78/100
SECURITY SCORE
Certificate Information
Subject
CN=lk4.us
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
November 02, 2025
Valid Until
January 31, 2026
60 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
6A:9F:3F:7A:C8:FB:05:9E:5C:1D:64:44:8F:02:C6:89:CE:C8:CB:98:15:A0:CE:22:8F:CF:02:1F:33:64:7C:14
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
Missing
Not configured
Content-Security-Policy
Basic
script-src; base-uri; object-src; +1 more
script-src 'self' 'nonce-4b3b116150984bbd8d84221b35cb2dea' 'report-sample' 'strict-dynamic' 'unsafe-inline'; base-uri 'self'; object-src 'none'; frame-ancestors 'self' https://short.io;
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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