Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=community.sailpoint.com
Issuer
C=US, O=Amazon, CN=Amazon ECDSA 256 M04
Valid From
December 18, 2025
Valid Until
January 16, 2027
348 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
36:97:5D:30:45:77:2F:2E:58:DC:4B:58:A2:A0:AC:13:F6:CB:D4:E0:E6:9B:36:B8:F9:C1:5B:4E:03:2A:81:01
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
connect-src; default-src; font-src; +5 more
connect-src https: wss:; default-src https:; font-src https: data:; frame-ancestors 'self'; img-src https: data: blob:; media-src https: blob:; script-src https: blob: 'unsafe-eval' 'unsafe-inline'; style-src https: blob: 'unsafe-inline';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
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 X-Content-Type-Options: nosniff
- • 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