Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
ClearBit
Cloudflare Turnstile
Decagon
Facebook
Firebase
Giscus
GitHub
Google API JS Client
Google Cloud Functions
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Sign-In
Google Tag Manager
G Workspace
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
jsDelivr
LinkedIn
Stripe
TikTok Analytics
Twitter
Vercel
YouTube
Google Cloud
Certificate Information
Subject
CN=beta.codeium.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 28, 2026
Valid Until
July 27, 2026
78 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A0:EA:16:BC:40:BC:67:34:9B:E8:16:D0:4E:8B:38:53:88:67:97:68:AA:B3:1E:56:31:36:2F:C3:5C:28:3D:B6
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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=()
Recommendations
- • 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