Open
Cached
·
just now
97/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
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=www.assemblyai.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
March 29, 2026
Valid Until
June 27, 2026
55 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
80:6F:3F:00:19:C2:E1:80:96:96:BF:D1:20:F2:FB:44:EB:E5:21:5B:EB:47:0B:6C:06:1E:32:29:C2:03:B1:4A
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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 4 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance