Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Google Trust
Microsoft Advertising
Calendly
Cloudflare CDNJS
Cookiebot
Facebook
Font Awesome
Google API JS Client
Google DoubleClick
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
jsDelivr
LinkedIn
Microsoft Clarity
OneTrust
Twitter
Vimeo
Wistia
YouTube
Google Cloud
Certificate Information
Subject
CN=connected.silverfin.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 16, 2026
Valid Until
July 15, 2026
71 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
02:F7:AB:42:67:82:84:E2:87:B1:BB:C8:9F:9F:5C:9A:3B:77:19:AC:E8:37:40:DA:F1:46:2F:9C:D6:9A:9C:C5
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=2592000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
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'
- • 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