Open
Cached
·
just now
84/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
C=US, ST=New York, O=REFINITIV US LLC, CN=*.complinet.com
Issuer
C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Organization Validation Secure Server CA
Valid From
October 25, 2025
Valid Until
October 25, 2026
69 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
50:F3:EA:B8:FC:14:58:14:26:B1:37:0E:A1:A7:C4:5A:90:D9:00:F8:F2:D4:91:81:4D:95:DC:0C:2B:FD:D6:F8
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Present
ALLOW-FROM http://thomsonreuterstax.lookbookhq.com, ALLOW-FROM https://thomsonreuterstax.lookbookhq.com, ALLOW-FROM http://answers.legalprof.thomsonreuters.com, ALLOW-FROM https://answers.legalprof.thomsonreuters.com, ALLOW-FROM http://app.accelus.com, ALLOW-FROM https://app.accelus.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • 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