Open
Cached
·
just now
75/100
SECURITY SCORE
Certificate Information
Subject
CN=etfagentic.com
Issuer
C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1
Valid From
May 08, 2026
Valid Until
November 22, 2026
180 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A9:67:82:F1:FC:89:35:C7:37:0C:69:76:05:3C:D7:87:9A:2D:79:D8:C8:CD:E1:8F:6C:A3:E7:1A:A3:9E:03:65
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • 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