Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
CN=dev.enelx.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 14, 2026
Valid Until
April 14, 2026
70 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
39:75:FB:96:FF:9F:E4:FA:EA:B5:EC:A9:C8:15:47:4E:40:3A:69:6D:2A:FE:3E:1F:17:F3:91:AB:D9:A3:75:43
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=63072000; includeSubDomains; preload
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Present
ALLOW-FROM https://www.enelx.com, ALLOW-FROM https://d3eepfzwqopgtx.cloudfront.net, ALLOW-FROM https://d13hhoqz1xnrhs.cloudfront.net, https://yourban.enelx.com, SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Significantly strengthen CSP directives
- • 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