Security report for indexcoop.com
Index Cooperative · Finance · N/a
Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.
Index Cooperative is a decentralized autonomous organization (DAO) focused on providing innovative DeFi products such as leveraged tokens and yield optimization strategies. The company positions itself as a market leader in on-chain structured products, offering automated and user-friendly tools for crypto investors and traders. Their product suite includes leverage tokens with built-in liquidation protection and smart looping strategies to amplify returns. The website demonstrates a high level of professionalism, with comprehensive content, strong branding, and clear navigation. Technically, the site is built using modern frameworks including Astro and React, with performance and mobile optimization rated as excellent. The use of advanced frontend technologies and integration with DeFi platforms like Ethereum and Arbitrum reflects a mature digital infrastructure. Analytics and error monitoring are implemented via Sentry, and cookie consent mechanisms are in place to ensure privacy compliance. From a security perspective, the project has undergone multiple independent smart contract audits and maintains an active bug bounty program through Immunefi, indicating a strong commitment to security best practices. The website enforces HTTPS and likely employs standard security headers, although explicit header details are not visible. No vulnerabilities or exposed sensitive data were detected in the analysis. Overall, the website and project present a low-risk profile with strong trust indicators, though the absence of WHOIS registrant data and explicit incident response contacts slightly reduce the business credibility score. Strategic recommendations include publishing clearer incident response contacts, security.txt files, and enhancing transparency around data protection roles to further strengthen trust and compliance.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 53/ 100 · Medium
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (j) Multi-factor authentication and secured communications: Not visible from outside
This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.
GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.
Priority findings
6 findings rated critical or high. Fix these first.
Security headers
Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.
- High
Missing X-Frame-Options header
Prevents clickjacking attacks
What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"
- CWE-1021
- OWASP A06:2025
- CAPEC-103
- ASVS V3.4.6
- OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
- RFC 7034
- High
Missing Content-Security-Policy header
Controls resources the browser is allowed to load
What to do: Implement a Content-Security-Policy appropriate for your application
- ASVS V3.4.3
- OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
- High
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- High
No Cookie Policy found
GDPR requires clear information about cookie usage
What to do: Add a dedicated cookie policy explaining cookie usage and purposes
- High
No Cookie Consent Banner found
GDPR requires explicit consent for non-essential cookies
What to do: Implement a cookie consent banner that appears on first visit
- GDPR Art. 7
- ePrivacy Art. 5(3)
- NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
- High
SSL/TLS
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
- High
Weak Protocols Supported
Server supports weak protocols: TLSv1.1
What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions
- CWE-327
- OWASP A04:2025
- ASVS V12.1.1
- RFC 8996
- RFC 7568
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: tls_versions TLSv1.2, TLSv1.3
- NIS2 21(2)(h)
- IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
- NIST SC-8(1): NIST SP 800-53 Rev. 5 SC-8(1): Cryptographic Protection
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching indexcoop.com
This scan found 24 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
Daily monitoring
Recommended€25per month
- TLS certificates and expiry
- DNS records
- SPF, DKIM and DMARC
- Security headers
- GDPR and NIS2 posture
- Exposed services
- Third-party trackers
- Security score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
Full report
€39.90one-time
- The complete analysis as a PDF you can cite
- Email delivery with an unlock code
- Lifetime access to this report
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
How this score is calculated
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
- SSL/TLS
- 72
- Security headers
- 30
- Email security
- 85
- DNS health
- 65
- Network security
- 100
- GDPR outside view
- 53
- Average
- 68
Not counted
- NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
- OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
- The certificate is not trusted by browsers
- The website is not served over HTTPS
- A database, remote desktop, file-sharing or Telnet service is reachable from the internet
- The page loads a script from a compromised source
- The domain registration has expired
- SPF authorises every server to send mail as the domain
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
- Critical0–25
- High26–49
- Medium50–75
- Low76–100
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- Publish explicit incident response contact information on the website to facilitate vulnerability reporting and security communication.
- Implement and publish a security.txt file to standardize vulnerability disclosure processes.
- Ensure all recommended security headers (Content-Security-Policy, X-Content-Type-Options, Referrer-Policy) are explicitly set and documented.
- Enhance transparency by providing data protection officer contact details or privacy compliance officer information.
- Maintain regular communication of audit results and security updates to reinforce user trust and compliance posture.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Index Cooperative
- Description
- Index Cooperative is a decentralized autonomous organization (DAO) specializing in creating and maintaining onchain structured products that enable users to earn more with automated DeFi yield and leverage. They offer smarter DeFi tools for yield and leverage, providing automated trading and investment products.
- Key services
- Leveraged tokens, Yield products, Automated rebalancing, DeFi lending market integration, Smart loops for yield amplification
- Content quality
- excellent
- Branding
- consistent
Technology
- Stack
- Astro, React, Tailwind CSS, Slick Carousel, Partytown
- Frameworks
- Astro, React
- Platforms
- Ethereum, Arbitrum, Base, Avalanche (implied by network IDs)
- Performance
- fast
- Mobile
- excellent
- Accessibility
- good
- SEO
- good
Security
- Observed score
- 90/100
- Good practices seen
- HTTPS enforced
- Multiple independent smart contract audits
- Bug bounty program active
- No exposed sensitive data in HTML
- Use of secure modern frameworks
Analytics and tracking
- Services
- Sentry
- Tracking level
- minimal
- Privacy practices
- good
Advertising
- Tracking pixels
- Sentry
- Marketing tools
- Sentry, Partytown
- Transparency
- good
Site quality
- Design
- excellent
- User experience
- excellent
- Content relevance
- excellent
- Navigation
- excellent
- Professionalism
- excellent
- Trustworthiness
- high
Key observations
- Website is fully accessible with rich content and no blocking detected.
- Strong focus on DeFi leveraged tokens and yield products.
- Multiple security audits and bug bounty program indicate good security posture.
- No direct company contact emails or phone numbers found on the site.
- Privacy and cookie policies are present with consent mechanisms.
- Modern tech stack with Astro and React used for frontend.
- No suspicious or malicious content detected.
- Social media presence on Twitter, LinkedIn, Discord, YouTube.
- No physical address or DPO contact found.
- WHOIS data is missing or privacy protected, common in crypto space.
Technical notes
Notes
Standards and sources
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with indexcoop.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review indexcoop.com.