Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Google Trust
Google AdSense
Zscaler
Google Tag Manager
Brightcove
Bing
Google Hosted Libraries
Recite Me
UKG
HubSpot Forms
Google DoubleClick
Google Analytics
Google Static File Front End
Leadfeeder
Google Fonts
LinkedIn
HubSpot Analytics
unpkg
Google Search
Facebook
Adobe Fonts (Typekit)
OpenWeatherMap
Cloudflare CDNJS
AWS
jQuery
Vimeo
IDX
Convert
PostHog
HubSpot
Equally AI
Highcharts
Microsoft Active Directory Federation Services
YouTube
Microsoft Clarity
jsDelivr
Google Cloud
Certificate Information
Subject
CN=viz.tools.investis.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 17, 2026
Valid Until
June 15, 2026
52 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
0E:8A:95:98:AD:63:86:59:7C:CF:49:EA:C9:C3:83:35:4B:17:0D:47:E2:CA:23:19:A7:2F:88:A4:6D:26:E4:2F
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
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), battery=(); +13 more
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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