Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=help.nice.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
August 28, 2025
Valid Until
September 26, 2026
268 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
34:0B:05:84:04:01:92:C6:3A:33:3D:48:8C:2F:AB:D3:A4:B2:ED:24:79:DB:B6:C0:50:1F:F6:5F:D0:36:BA:E6
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
upgrade-insecure-requests; default-src; connect-src; +1 more
upgrade-insecure-requests; default-src https: data: filesystem: blob: mediastream: 'unsafe-inline' 'unsafe-eval'; connect-src https: wss:; frame-ancestors 'self'
X-Frame-Options
Good
SAMEORIGIN
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