Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=beta.fitbit.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
March 24, 2025
Valid Until
April 22, 2026
95 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
E1:17:8A:B8:01:D7:13:6B:FD:BC:FB:85:9D:16:CB:E7:2E:D8:BD:ED:0A:66:3F:8D:93:71:6A:7D:7F:DF:06:D7
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; img-src; +4 more
upgrade-insecure-requests; default-src https://*; img-src https://* blob:; media-src https://* blob:; worker-src https://* blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*; style-src 'self' 'unsafe-inline' https://*;
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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