SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for *.e2open.com, e2open.com, not for cdmsolutions.chg.e2open.com
Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Texas, L=Austin, O=E2open, LLC, CN=*.e2open.com
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
September 08, 2025
Valid Until
September 08, 2026
216 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F0:1D:B3:34:93:60:94:0A:CD:8E:6E:FA:BF:8B:04:37:18:FF:C7:11:D1:FD:48:D0:0B:AB:0A:91:A2:C8:BF:BD
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Excellent
max-age=31536000;includeSubDomains;preload
Content-Security-Policy
Basic
default-src; script-src; img-src; +4 more
default-src 'self' e2open.com *.e2open.com wss://*.e2open.com blob:; script-src 'unsafe-inline' 'unsafe-eval' 'self' e2open.com *.e2open.com wss://*.e2open.com blob:; img-src 'self' e2open.com *.e2open.com wss://*.e2open.com blob: data:; style-src 'self' 'unsafe-inline' e2open.com *.e2open.com wss://*.e2open.com; font-src 'self' data:; form-action 'self' e2open.com *.e2open.com wss://*.e2open.com; frame-ancestors 'self' e2open.com *.e2open.com wss://*.e2open.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • 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