Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
CN=cloud4feed.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 23, 2025
Valid Until
March 23, 2026
81 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
6E:E7:F6:04:80:A6:B3:23:07:2F:C3:5A:A9:D8:31:EA:4A:A0:4C:88:43:8B:88:94:93:AF:B5:C7:AF:64:87:2A
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Excellent
max-age=64072000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
no-referrer, strict-origin-when-cross-origin
Permissions-Policy
Present
clipboard-read=(self), geolocation=(self), camera=(self), microphone=(self), clipboard-write=(self), payment=(), usb=(), display-capture=(self)
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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