Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=themindaction.com
Issuer
C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1
Valid From
June 22, 2026
Valid Until
January 06, 2027
143 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
30:F6:5B:46:4F:6D:43:70:21:86:91:6E:BE:4D:95:0E:B4:93:5E:4A:BA:9E:EA:1A:13:E2:B9:25:5D:4D:7C:52
Alternative Names
Security Configuration
TLS Protocols
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
X-Frame-Options
Present
ALLOW-FROM https://app.kajabi.com https://app.vibely.io https://communities.kajabi.com https://communities-widget.kajabi.com *.mykajabi.com https://communities.newkajabi-staging.com https://communities-widget.newkajabi-staging.com https://game.themindaction.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Significantly strengthen CSP directives
- • 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