Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=cloud.collaboradmins.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 15, 2026
Valid Until
April 15, 2026
80 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
18:BD:BD:67:CF:6A:22:EC:D5:08:A9:54:50:A4:DC:DC:B2:D3:63:66:B5:FE:3B:C8:7D:2D:B6:3A:9F:E2:3B:A9
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=15768000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; script-src; style-src; +7 more
default-src 'self'; script-src 'self' 'nonce-uBD3Za8wr4He0wNMLTsdfbpVc3tlnzC2ke2oj9wjWrM='; style-src 'self' 'unsafe-inline'; frame-src *; img-src * data: blob:; font-src 'self' data:; media-src *; connect-src *; object-src 'none'; base-uri 'self';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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