Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=sorryapp.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 05, 2025
Valid Until
February 03, 2026
58 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DD:81:45:AE:48:B8:25:69:B6:D7:8C:52:97:F8:AB:B6:39:BE:42:3F:7B:66:A2:46:50:75:6A:98:FD:34:D5:E0
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
Basic
base-uri; block-all-mixed-content; frame-ancestors; +4 more
base-uri 'none'; block-all-mixed-content; frame-ancestors 'none'; object-src 'none'; script-src 'unsafe-inline' 'unsafe-eval' 'strict-dynamic' https:; upgrade-insecure-requests; report-uri https://f08c81a681d074ab5fd23f897fe43f29.report-uri.com/r/d/csp/enforce
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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
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