Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 73, 84>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 6, 66, 105, 101, 108, 108, 97>>}, UNKNOWN={:asn1_OPENTYPE, <<12, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, UNKNOWN=BI - 202965, C=IT, ST=Piemonte, L=BIELLA, O=FABRICK S.P.A., CN=dashboard.fabrick.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1
Valid From
April 23, 2025
Valid Until
April 23, 2026
84 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
DF:DB:F8:96:07:40:C6:94:CA:94:8A:86:C8:7C:A7:94:27:DE:9D:DD:69:7E:71:DF:58:16:EB:18:9B:48:DE:73
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Good
upgrade-insecure-requests; object-src; base-uri; +7 more
upgrade-insecure-requests; object-src 'none'; base-uri 'self'; default-src 'self'; script-src 'self' 'nonce-aXufsWFFH38hHPq1189AxAAAAXk' 'strict-dynamic' 'unsafe-inline' *.fabrick.com; style-src 'self' https://*.hotjar.com 'unsafe-inline' fonts.googleapis.com fonts.gstatic.com *.fabrick.com; font-src 'self' fonts.googleapis.com fonts.gstatic.com https://*.hotjar.com; frame-src 'self' *.sella.it *.gestpay.net *.fabrick.com *.cookiebot.com; img-src 'self' *.sella.it *.gestpay.net cdn.cookielaw.org data: *.cookiebot.com https://*.hotjar.com; connect-src 'self' *.sella.it *.gestpay.net *.fabrick.com *.axerve.com cdn.cookielaw.org *.onetrust.com *.cookiebot.com *.acsbapp.com *.upflowadv.com https://*.hotjar.com https://*.hotjar.io wss://*.hotjar.com;
X-Frame-Options
Good
SAMEORIGIN
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
- • Strengthen CSP by removing 'unsafe-eval'
- • 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