SSL/TLS Analysis for hibernate.org
Analyzed on November 02, 2025 at 11:56 UTC
Security Score
89
/
100
Certificate Information
Subject
CN=hibernate.org
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
October 29, 2025
Valid Until
January 27, 2026
85 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
07:74:89:33:52:EF:CC:6F:1D:30:97:A7:E9:32:F6:04:34:99:71:2E:7B:8B:DB:DD:B3:F1:F5:4B:30:2E:2E:DC
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=15768000; includeSubDomains; preload
Content-Security-Policy
Basic
default-src; form-action; base-uri; +7 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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