Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=cloud.ccdigitalab.com
Issuer
C=US, O=Let's Encrypt, CN=YE2
Valid From
June 15, 2026
Valid Until
September 13, 2026
35 days
Public Key
ECDSA
384 bit
(P-384)
Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
8F:72:8D:C6:E8:E4:84:53:87:40:87:B7:E9:39:EA:C6:E0:9B:94:E3:E8:95:C3:DB:B2:A0:81:1E:B3:20:05:70
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=63072000; preload
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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