Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Adobe Fonts (Typekit)
Akamai
AWS
Clickagy
Cloudflare CDNJS
Crazy Egg
Facebook
Google Analytics
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
IP-API
LinkedIn
Quora
Sectigo
The Trade Desk
Twitter
Vimeo
YouTube
ZoomInfo
Google Cloud
Microsoft Azure
Certificate Information
Subject
CN=*.znode.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36
Valid From
January 22, 2026
Valid Until
January 09, 2027
247 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
6B:00:D1:C0:32:EC:75:F4:9D:A3:B9:6C:BC:38:6A:59:6B:3A:BC:63:04:92:F7:49:5A:5D:FC:BE:6C:F6:D7:D6
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
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Content-Type-Options: nosniff
- • 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