Open
Cached
·
just now
80/100
SECURITY SCORE
Detected Technologies
Google Trust
Amplitude
Atlassian
AWS
Amazon S3
Bugsnag
Cloudflare CDNJS
Contentful
Fullstory
G2
Google API JS Client
Google Cloud Storage
Google Fonts
Google Hosted Libraries
Google Static File Front End
Google Sign-In
ipify
LaunchDarkly
Active incidents
Pendo
Salesforce Personalization
Salesforce Cloud
Salesforce Sites
Zendesk
Google Cloud
Certificate Information
Subject
CN=apps.bettercloud.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
March 16, 2026
Valid Until
June 14, 2026
45 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
53:D1:6A:34:88:EA:E9:6F:D9:24:64:79:21:4B:13:4C:B1:40:E6:E7:48:60:FF:82:00:ED:8C:D0:B2:05:92:82
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
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • 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