Security report for yeco.io
ScreenForge Ltd trading as Yeco · Technology · Ireland
Medium risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.
Yeco, operated by ScreenForge Ltd, offers a specialized touch control software solution for Ableton Live users, integrating MIDI controllers for Windows and macOS platforms. The product targets musicians and producers seeking a natural and fluid workflow on touchscreen devices. The website presents a professional and content-rich experience with multimedia demonstrations and clear calls to action for trial and purchase. Technically, the site is built on the Webydo platform, leveraging standard web technologies and third-party analytics and marketing tools such as Facebook Pixel and Hotjar. However, the absence of HTTPS and use of outdated JavaScript libraries represent notable security weaknesses. Privacy compliance is addressed with a cookie consent banner and linked privacy policy, though terms of service and security policies are missing. Overall, the business appears legitimate with consistent WHOIS data and reputable payment processing partnerships.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 40/ 100 · High
- 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
7 findings rated critical or high. Fix these first.
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Critical
No HTTPS encryption
GDPR requires appropriate security measures for personal data
What to do: Implement SSL/TLS certificate for HTTPS
- CWE-319
- OWASP A04:2025
- ASVS V12.2.1
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- GDPR Art. 32(1)(a)
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- High
No Privacy Policy found
GDPR requires a clear and accessible privacy policy
What to do: Add a comprehensive privacy policy page and link to it prominently
- GDPR Art. 12
- GDPR Art. 13
- NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- High
Third-party services without privacy policy
Detected services: Facebook, Twitter, YouTube, Cloudflare, Google Ads
What to do: Document all third-party data sharing in your privacy policy
- Critical
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.
- Critical
No HTTPS Encryption
Website does not use HTTPS encryption, making all data transmission vulnerable to interception
What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS
- CWE-319
- OWASP A04:2025
- ASVS V12.2.1
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- GDPR Art. 32(1)(a)
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- Critical
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 Strict-Transport-Security header
Forces HTTPS connections
What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"
- CWE-319
- OWASP A04:2025
- ASVS V3.4.1
- RFC 6797 §6.1.1
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: hsts_min_age 63072000
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- 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
Need hands-on remediation? Email guard@offseq.com
Keep watching yeco.io
This scan found 20 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
- 0
- Security headers
- 15
- Email security
- 70
- DNS health
- 75
- Network security
- 100
- GDPR outside view
- 40
- Average
- 50
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
- Implement HTTPS across the entire website with a valid SSL certificate to secure user data and improve trust.
- Update all JavaScript libraries, especially jQuery, to the latest secure versions to mitigate known vulnerabilities.
- Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
- Publish clear security and incident response policies, including contact channels for reporting security issues.
- Enhance mobile optimization and accessibility to improve user experience and compliance with best practices.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- ScreenForge Ltd trading as Yeco
- Description
- Yeco is a touch controller software for Ableton Live that integrates MIDI controllers for Windows and Mac, designed to speed up workflow and enable natural music creation on touchscreen devices.
- Key services
- Touch control software for Ableton Live, Integrated MIDI controllers, Multi-touch interface, Free trial and purchase options
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- HTML5, CSS3, JavaScript, jQuery 1.7.2, YouTube embedded videos, Facebook Pixel, Hotjar, CookieConsent plugin
- Frameworks
- Webydo (website builder platform)
- Platforms
- Windows, macOS
- Performance
- moderate
- Mobile
- basic
- Accessibility
- basic
- SEO
- basic
Security
- Observed score
- 50/100
- Good practices seen
- Cookie consent banner implemented
- No exposed sensitive data in HTML
Analytics and tracking
- Services
- Facebook Pixel, Hotjar, Google DoubleClick
- Tracking level
- moderate
- Privacy practices
- basic
Advertising
- Tracking pixels
- Facebook Pixel, Hotjar
- Marketing tools
- Facebook Pixel, Hotjar, CookieConsent plugin
- Transparency
- basic
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- moderate
Key observations
- Website is fully accessible with rich content and multimedia
- No HTTPS detected in provided HTML content, which is a critical security concern
- Use of older JavaScript libraries may pose security risks
- Cookie consent and privacy policy are implemented and linked
- No explicit terms of service or security policy pages found
- Contact information is primarily via contact form and newsletter signup
- Social media presence is active on Twitter, Instagram, YouTube, and Facebook
- Payment processing is handled by FastSpring, a reputable third party
- Website built using Webydo platform
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 yeco.io. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review yeco.io.