Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=zwift.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
July 08, 2025
Valid Until
August 06, 2026
179 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C8:19:2A:E9:AF:6E:73:89:8E:F5:3B:3F:24:F7:28:F3:45:D1:3E:FC:A5:0C:51:9C:0E:47:38:C8:BB:99:9C:4F
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
Present
max-age=15552000; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • 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
Subject Alternative Names
10 domains
zwift.com
*.zwift.com
gozwift.com
*.gozwift.com
zwift.ca
*.zwift.ca
zwiftacademy.com
*.zwiftacademy.com
zwiftblog.com
*.zwiftblog.com
Other domains in certificate