Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=data.sendbird.com
Issuer
C=US, O=Google Trust Services, CN=WR1
Valid From
December 15, 2025
Valid Until
March 15, 2026
75 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
41:6E:0E:AF:0E:94:CA:81:24:D3:DD:E8:78:1A:FB:68:6A:3B:55:34:63:F8:DB:A2:B9:0E:9A:79:A3:C2:49:C3
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
object-src; script-src; base-uri; +1 more
object-src 'none'; script-src 'nonce-ODExYmY1NzE2YzJlZWI0YWVmMDEwYjc1MDE1ZTc4ZDk=' 'unsafe-inline' 'unsafe-eval' 'report-sample' 'strict-dynamic' https: blob:; base-uri 'self'; report-uri https://csp.withgoogle.com/csp/looker/v1
X-Frame-Options
Missing
Not configured
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 X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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