Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=enjoy.ly
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 10, 2025
Valid Until
March 10, 2026
57 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F2:D2:FE:D9:34:AF:52:4D:4B:BD:B2:1A:44:22:7E:70:8A:35:70:A7:7D:5A:6F:61:79:9F:92:F5:BD:DA:57:48
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=31557600
Content-Security-Policy
Good
default-src; script-src; connect-src; +6 more
default-src 'self' blob:;script-src 'self' 'unsafe-inline' blob: https:;connect-src https: wss:;frame-src https:;object-src 'none';font-src 'self' https: data:;style-src 'self' https: 'unsafe-inline';img-src 'self' data: https: blob:;upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
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