Open
Cached
·
6m ago
75/100
SECURITY SCORE
Certificate Information
Subject
CN=api.sportradar.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
February 06, 2025
Valid Until
March 08, 2026
123 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E0:F5:AC:BE:A6:55:B6:80:E5:2B:5C:7C:A7:F5:C3:F9:55:33:59:30:97:B5:94:3C:14:81:64:76:A3:3B:73:F4
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
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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
Subject Alternative Names
6 domains
api.sportradar.com
api.sportradar.us
api.sportsdatallc.com
api.sportsdatallc.org
srsmtdelivery.com
*.srsmtdelivery.com
Other domains in certificate