Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=support.linology.tech
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
December 08, 2025
Valid Until
March 08, 2026
50 days
Public Key
ECDSA
384 bit
(P-384)
Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
0F:CC:D8:B6:56:E5:9D:78:00:86:F8:82:44:02:41:21:5B:2A:18:01:B0:3E:77:5F:50:FB:96:D5:87:8C:97:47
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
Missing
Not configured
Content-Security-Policy
Basic
base-uri; default-src; font-src; +5 more
base-uri 'self' http://support.linology.tech; default-src 'self' ws: wss: https://images.zammad.com; font-src 'self' data:; img-src * data: blob:; object-src 'none'; script-src 'self' 'unsafe-eval' 'nonce-Bk56KrtNxF7A9bZtw90fbQ=='; style-src 'self' 'unsafe-inline'; frame-src www.youtube.com player.vimeo.com
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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