Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=systematic.workato.com
Issuer
C=US, O=Amazon, CN=Amazon ECDSA 256 M01
Valid From
December 18, 2025
Valid Until
January 16, 2027
386 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
51:D1:2B:39:FA:F7:CD:A0:3C:C7:B0:53:2B:0D:C9:6B:00:DE:57:67:CD:F4:76:48:A9:2F:E5:63:1D:16:50:DC
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; frame-ancestors; +3 more
connect-src https: wss:; default-src https:; frame-ancestors 'none'; img-src https: data: blob:; script-src https: 'unsafe-eval' 'unsafe-inline'; style-src https: blob: 'unsafe-inline';
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