Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
Microsoft Advertising
Cloudflare CDNJS
Cookiebot
CookieFirst
Crisp
Facebook
FirstPromoter
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
jQuery
jsDelivr
LinkedIn
Microsoft Clarity
Sentry
TikTok Analytics
unpkg
Wistia
YouTube
Google Cloud
Certificate Information
Subject
CN=onestream.live
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
April 29, 2026
Valid Until
July 28, 2026
76 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
8E:87:2E:10:15:F9:50:35:D8:58:35:BE:FB:D0:60:C1:0E:FD:D9:DC:91:9F:93:09:38:21:42:A5:8D:CC:5E:93
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
interest-cohort=()
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
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