Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Google AdSense
Google Tag Manager
G2
Command AI
Netlify
HubSpot Forms
Google DoubleClick
Arcade
Google Analytics
Google Conversion Tracking
ClearBit
6sense
Segment
Google Fonts
Vidyard
Wistia
Twitter
Loom
LinkedIn
Stripe
HubSpot Analytics
unpkg
Google Search
Facebook
Heap
Vimeo
Statsig
Google Optimize
Akamai
HubSpot
Intercom
Quora
YouTube
Font Awesome
HubSpot Live Chat
Sentry
jsDelivr
Certificate Information
Subject
CN=labs.commandbar.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
December 29, 2025
Valid Until
March 29, 2026
35 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
5A:54:04:A9:4D:A0:65:DB:88:FF:63:26:22:D9:A3:9D:14:16:31:B5:63:7A:41:20:69:66:A8:04:8E:B1:FF:7B
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=63072000; includeSubdomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
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