Cached · just now
78/100 SECURITY SCORE

Certificate Information

Subject
CN=go.cerifi.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
May 23, 2026
Valid Until
August 21, 2026 70 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D2:A9:89:2C:79:D2:AF:A4:5E:7C:1C:9D:22:40:0C:AD:A8:EB:78:18:F9:18:82:2E:F8:41:32:62:32:33:D8:FE
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
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Add Strict-Transport-Security header with max-age of at least 1 year
  • Add Content-Security-Policy header to prevent XSS attacks
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Add X-Content-Type-Options: nosniff
  • 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
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
letsencrypt.org ; validationmethods=http-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/23216805 awstrust.com digicert.com
Incident Reporting
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

1 domain