Cached · just now
91/100 SECURITY SCORE

Certificate Information

Subject
CN=statsig.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 15, 2026
Valid Until
April 15, 2026 50 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
58:F6:92:14:3A:41:99:07:B9:33:83:D4:BB:DD:F8:FB:2F:C9:DE:14:62:6E:34:92:55:02:0C:BA:D1:A8:5F:BB
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors Analyze
Content-Security-Policy-Report-Only
Weak
base-uri; script-src-elem; report-uri; +2 more Analyze
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
browsing-topics=()
Recommendations
  • Consider adding 'preload' to HSTS for maximum security
  • 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