Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=ezable.com
Issuer
C=US, O=DigiCert, Inc., CN=Encryption Everywhere G3 TLS ECC P384 SHA384 2023 CA1
Valid From
July 05, 2025
Valid Until
July 04, 2026
153 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
C2:B3:F0:21:33:27:EF:6E:E2:7E:D5:00:89:51:DD:C0:1A:69:CC:9C:31:22:D1:FC:96:4F:47:44:90:83:F4:54
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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