Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Google Trust
Adobe Fonts (Typekit)
Cloudflare CDNJS
Convert
Crazy Egg
Facebook
Google Analytics
Google Tag Manager
Hotjar
HubSpot
Active incidents
HubSpot Analytics
Active incidents
HubSpot Feedback & Surveys
Active incidents
HubSpot Forms
Active incidents
HubSpot Live Chat
Active incidents
Twitter
Vidyard
Certificate Information
Subject
CN=hubapi.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 22, 2026
Valid Until
July 21, 2026
80 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
9F:EB:9E:D0:5E:B4:94:9E:BD:42:83:3D:05:13:85:93:5E:DE:D4:3A:DE:C3:4C:D9:01:C7:53:21:8D:7A:E9:0D
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
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Significantly strengthen CSP directives
- • 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