Open
Cached
·
just now
87/100
SECURITY SCORE
Detected Technologies
Google Trust
Instagram
YouTube
Google AdSense
Chili Piper
Google Tag Manager
Google Sign-In
Cometly
Amplitude
Mux
Fullstory
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Pusher
Sprig
New Relic
Typeform
Google Cloud Storage
Google API JS Client
Google Fonts
Twitter
G Workspace
LinkedIn
Zendesk
Contentful
Cloudinary
Stripe
Drift
unpkg
Fastly
Google Search
Facebook
OneTrust
Customer.io
Pinterest
Cloudflare CDNJS
MNTN
Akamai
Active incidents
FirstPromoter
Sentry
Certificate Information
Subject
CN=streamyard.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 09, 2026
Valid Until
July 08, 2026
65 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
08:92:19:72:41:8F:C0:60:A1:38:EA:13:9B:82:08:47:AB:89:0E:3E:29:A2:75:BC:1E:5A:AB:B4:0B:A6:1B:0B
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
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
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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