Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=palazzoli.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 01, 2026
Valid Until
April 01, 2026
77 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5A:4F:1F:5C:97:60:99:CC:4A:91:E7:C1:C2:65:28:B8:0F:D4:3E:77:D2:90:F9:15:0E:D0:0A:CC:52:F1:C7:F6
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
default-src; script-src; object-src; +5 more
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' *.google.com *.googleapis.com *.googletagmanager.com *.gstatic.com *.iubenda.com *.fontawesome.com *.google-analytics.com *.jquery.com *.bootstrapcdn.com cdnjs.cloudflare.com *.hotjar.com *.facebook.net *.facebook.com; object-src 'self'; style-src 'self' 'unsafe-inline' *.googleapis.com *.jquery.com *.fontawesome.com *.bootstrapcdn.com cdnjs.cloudflare.com; img-src 'self' data: blob: *.gstatic.com *.google-analytics.com *.googletagmanager.com *.googleapis.com *.jquery.com *.iubenda.com *.facebook.com; frame-src 'self' *.google.com *.iubenda.com *.youtube-nocookie.com *.hotjar.com; font-src 'self' data: *.gstatic.com *.fontawesome.com *.bootstrapcdn.com script.hotjar.com; connect-src 'self' blob: *.google.com *.google-analytics.com *.hotjar.com *.hotjar.io wss://*.hotjar.com *.iubenda.com *.doubleclick.net *.facebook.com maps.googleapis.com
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
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'
- • 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