87/100 SECURITY SCORE

Certificate Information

Subject
CN=zappysoftware.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 05, 2026
Valid Until
April 05, 2026 83 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
9F:B2:5D:CA:F8:88:EA:76:D3:D7:81:1F:B3:D3:16:2B:E1:E0:5B:D3:83:FF:18:CC:EB:95:3F:A2:30:D9:78:D2
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Present
ALLOW-FROM https://*.zappy.dev https://*.zappy.pro https://*.zappysoftware.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
cross-origin-isolated=(self), keyboard-map=(self), navigation-override=(self), screen-wake-lock=(self), clipboard-read=(self), focus-without-user-activation=(self), idle-detection=(self), window-placement=(self), vertical-scroll=(self)
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives

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