Open Cached · just now
86/100 SECURITY SCORE

Certificate Information

Subject
CN=availability.healthwise.net
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
October 24, 2025
Valid Until
January 22, 2026 44 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A0:C5:38:D5:F0:82:9A:7E:E9:C2:48:36:B7:D9:C6:99:52:66:30:25:11:05:B0:9A:DA:A7:9C:83:FB:70:E4:B2
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=259200
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
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
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
  • Consider adding 'issuewild' records to control wildcard certificate issuance