Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Google Trust
Adobe Fonts (Typekit)
Adobe Marketo
Ahrefs
Bing
Cloudflare CDNJS
Drift
Font Awesome
Google Analytics
Google Fonts
Google Maps
Google Optimize
Google reCAPTCHA
Google Tag Manager
Hotjar
jQuery
jsDelivr
LinkedIn
Maze
Microsoft Clarity
OneTrust
PathFactory
Qualtrics
SalesLoft
Storylane
unpkg
Vidyard
Visual Website Optimizer
YouTube
Certificate Information
Subject
CN=fiixsoftware.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 17, 2026
Valid Until
July 16, 2026
65 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F3:7B:95:4F:52:B9:30:71:8F:67:10:90:BE:09:BF:B9:FA:90:00:CA:C7:71:60:C1:59:C1:DF:DD:C6:B4:D6:30
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
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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