93/100 SECURITY SCORE

Certificate Information

Subject
CN=connect.e2open.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
December 11, 2025
Valid Until
March 11, 2026 32 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
96:40:7D:6F:80:EB:E9:FB:98:68:ED:0C:95:20:D3:9A:92:E8:5A:C2:FF:ED:04:3C:DB:C8:3C:09:5B:E1:B0:FA
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
Basic
default-src; script-src; style-src; +13 more
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
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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

Subject Alternative Names

1 domain