Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=my.e2open.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 17, 2026
Valid Until
April 17, 2026
70 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
4E:E3:E2:BE:CF:F3:B4:7E:71:6D:89:F7:F4:CE:38:2E:B1:94:4C:AF:DB:68:C6:0C:DD:7B:97:24:8F:77:1A:04
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
Excellent
max-age=31622400; includeSubDomains; preload
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(), autoplay=(*), camera=(), display-capture=(), encrypted-media=(self), fullscreen=(self), geolocation=(*), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(self), picture-in-picture=(), publickey-credentials-get=(), usb=(self)
Recommendations
- • Significantly strengthen CSP directives
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