Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Ohio, L=Westlake, O=HYLAND SOFTWARE, INC., CN=*.alfresco.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign GCC R6 OV TLS CA 2023
Valid From
January 08, 2025
Valid Until
February 09, 2026
94 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
F3:D6:9F:EF:A3:E4:4C:3B:D4:B5:BE:00:BB:2B:08:D4:BB:31:43:31:E6:D7:D8:04:69:04:F4:43:B7:6C:64:F1
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
default-src; script-src
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