Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Gravatar
AWS CloudFront
Let's Encrypt
Ashby
Google Tag Manager
Reddit
HubSpot Forms
Google DoubleClick
AdRoll
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Greenhouse
Typeform
Calendly
Google API JS Client
Google Fonts
Wistia
Twitter
LinkedIn
HubSpot Analytics
Adobe Marketo
Demandbase
Facebook
Amazon S3
OneTrust
NitroPack
Cloudflare CDNJS
Active incidents
AWS
jQuery
TechTarget
HubSpot
YouTube
Font Awesome
Sentry
jsDelivr
Certificate Information
Subject
CN=bettercloud.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
March 12, 2026
Valid Until
June 10, 2026
43 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
AA:B3:65:A7:C6:94:BC:85:73:AC:46:2F:3A:4A:E4:3C:39:06:67:26:C4:1E:8E:FA:2E:A1:83:93:C3:AC:1A:40
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" env=HTTPS
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