Open
Cached
·
3h ago
84/100
SECURITY SCORE
Certificate Information
Subject
CN=www.feapricepulse.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 23, 2026
Valid Until
April 23, 2026
79 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
78:82:13:B7:CB:D4:69:71:7B:B8:94:FD:47:F9:7C:A3:D8:40:ED:00:51:40:B8:18:5E:59:DF:25:C7:3F:00:43
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
Weak
frame-ancestors
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), autoplay=(self), camera=(self), encrypted-media=(self), fullscreen=(*), geolocation=(*), microphone=(), midi=(self), payment=(self), display-capture=(self)
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Significantly strengthen CSP directives
- • 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