Open Cached · just now
88/100 SECURITY SCORE

Certificate Information

Subject
CN=cf-test.puppet.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
September 28, 2025
Valid Until
December 27, 2025 54 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BB:2F:4D:B1:0F:65:CC:77:6B:10:F7:3A:0E:7B:1C:8A:2A:62:46:AD:02:8C:FA:7E:50:98:38:4B:0E:ED:13:9F
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=300
Content-Security-Policy
Weak
report-uri; upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives
  • 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
sectigo.com awstrust.com digicert.com ; cansignhttpexchanges=yes pki.goog ; cansignhttpexchanges=yes letsencrypt.org
Wildcard CAs
digicert.com ; cansignhttpexchanges=yes awstrust.com sectigo.com letsencrypt.org pki.goog ; cansignhttpexchanges=yes
Incident Reporting
Recommendations
  • Consider using critical flag (flags=128) for stricter CAA enforcement
  • You have authorized 5 CAs - consider limiting to only the CAs you actively use