Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
Azure Blob Storage
Beamer
Cloudflare
Active incidents
Cloudflare CDN
Drift
Embedly
Active incidents
Google Analytics
Google Hosted Libraries
Google Maps
Google Static File Front End
Google Tag Manager
HubSpot
Intercom
jsDelivr
LaunchDarkly
LiveChat
Localize.js
LogRocket
Microsoft 365
Mixpanel
Microsoft SharePoint
Tawk.to
Zendesk
Google Cloud
Certificate Information
Subject
CN=www.help.emberit.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 22, 2026
Valid Until
July 21, 2026
72 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D9:6E:1E:B0:5F:D0:1C:9D:B6:91:76:EE:4D:11:ED:30:86:8D:17:11:60:EF:80:65:CB:14:B6:E7:A6:08:44:6E
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
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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