Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
YouTube
Chili Piper
Google Tag Manager
G2
Sanity
Reddit
Capterra
SoundCloud
Google DoubleClick
Google Analytics
ClickCease
Microsoft Advertising
Google Conversion Tracking
Mixpanel
Active incidents
Segment
Google Static File Front End
Google API JS Client
Google Fonts
Wistia
Twitter
Algolia
Hotjar
LinkedIn
Drift
Google Search
Storylane
Facebook
Adobe Fonts (Typekit)
Salesforce Pardot
Visual Website Optimizer
Vimeo
Google Optimize
Microsoft Clarity
Google Cloud
Certificate Information
Subject
CN=www.openlms.net
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
April 20, 2026
Valid Until
July 19, 2026
64 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
48:96:F7:4F:40:B6:5F:A3:CF:3C:79:53:70:1B:1F:0F:A5:9F:15:89:60:7F:7C:49:D1:8D:47:02:B3:A1:82:31
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
Present
max-age=31536000
X-Frame-Options
Present
ALLOW-FROM https://open-lms-studio.netlify.app
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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