Open
Cached
·
just now
94/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Active incidents
YouTube
Google Tag Manager
Bing
G2
RudderStack
Google Hosted Libraries
Webflow
Cello
Google DoubleClick
Google Analytics
Google Conversion Tracking
Pusher
Greenhouse
Datadog
Railway
Google Fonts
Twitter
Hotjar
LinkedIn
Cloudinary
Backblaze B2
Slack
unpkg
Airtable
Google Search
highlight.js
Embedly
Active incidents
OneTrust
GitHub
Cloudflare CDNJS
Vercel
Render
Microsoft Clarity
Font Awesome
Sentry
jsDelivr
Certificate Information
Subject
CN=chat.assemblyai.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 17, 2026
Valid Until
July 16, 2026
66 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
14:0A:62:45:B5:40:78:9A:65:45:84:F6:93:DB:19:5B:59:2F:0C:3D:9B:19:EA:48:B7:20:BA:02:47:4B:DF:37
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
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
autoplay=(self), geolocation=(self), clipboard-read=(self); +1 more
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
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