Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=cloud.sadfish.io
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
October 25, 2025
Valid Until
January 23, 2026
52 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
2E:A4:C8:DE:D9:C4:B0:CC:7F:97:67:AC:DC:44:7B:9A:BA:16:C9:84:B4:F6:3B:CE:D2:0B:5A:05:65:34:94:0E
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
Good
default-src; script-src; style-src; +7 more
default-src 'self'; script-src 'self' 'nonce-MG15VGFGOWRkTlA4NHNSSXdYM1FDTDVuWEY5ZC9jaWQ4SjhVVTlCVTZpOD06Z1NHZ1BBOWxFN1NPdEtBcmpoZVlXTmNzSmowcXI2VHhoS2xZSHFSam5YND0='; style-src 'self' 'unsafe-inline'; frame-src *; img-src * data: blob:; font-src 'self' data:; media-src *; connect-src *; object-src 'none'; base-uri 'self';
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Strengthen CSP by removing 'unsafe-eval'
- • 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