Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=my.pima.app
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 10, 2026
Valid Until
April 10, 2026
58 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C9:3A:26:C8:6E:42:EC:23:04:1D:7A:0F:FB:EF:E5:A5:8E:74:B0:6E:91:C5:83:BD:67:F5:6E:8B:A6:16:B3:56
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
Good
default-src; font-src; img-src; +4 more
default-src 'self' https:; font-src 'self' https: data:; img-src 'self' https: data:; object-src 'self' https:; script-src 'self' https: 'nonce-wuci+Js5o5YVuAlh/k13YQ=='; style-src 'self' https: 'unsafe-inline'; frame-ancestors 'self'
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Strengthen CSP by removing 'unsafe-eval'
- • Consider adding Permissions-Policy to control browser features
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