Security report for flock.io
FLock · Technology · N/a
Medium risk. 11 critical or high findings in Security headers, GDPR compliance and 3 other checks.
57/100
Risk levelMedium
FLock.io is a technology-focused platform aiming to provide decentralized, privacy-preserving solutions for artificial intelligence through federated machine learning integrated with blockchain technology. The website presents a professional and modern interface targeting developers, AI researchers, and enterprises interested in advanced AI training and deployment. The platform offers live AI models and training capabilities, positioning itself as a niche player in decentralized AI innovation. Technically, the website is built using modern frameworks such as Next.js and React, with UI components from Ant Design. Hosting includes Supabase for media content. The site is moderately optimized for performance and mobile responsiveness, with good SEO practices. However, accessibility features are basic, and some security best practices like security headers are missing. From a security perspective, the site uses HTTPS but lacks visible security headers and explicit privacy or cookie policies. WHOIS data is not publicly available, indicating privacy protection, which is common but reduces transparency. No contact or incident response information is provided, and no vulnerability disclosure or security.txt files are found. Overall, the security posture is moderate but could be improved with better transparency and policy disclosures. The overall risk assessment suggests a legitimate technology project with room for improvement in privacy compliance and security transparency. Strategic recommendations include implementing comprehensive privacy and cookie policies, adding security headers, publishing contact and incident response details, and improving WHOIS transparency to enhance trust and compliance.
Scanned
NIS2 and GDPR posture
- NIS2 posture
- 2/ 100 · Critical
- GDPR posture
- 53/ 100 · Medium
- Checks completed
- 7of 7
Indicative only: based on publicly visible signals, not a certification or legal assessment. NIS2 signals relate to Article 21 of Directive (EU) 2022/2555; GDPR signals to Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive.
Priority findings
11 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 compliance
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
NIS2 compliance
NIS2 expects organisations in scope to show basic security hygiene. These public signals are what an auditor or customer sees first.
- High
No information security framework found
NIS2 requires documented cybersecurity and information security measures
What to do: Implement and document information security policies and procedures
- NIS2 21(2)(a)
- IR 2024/2690 1.1: Implementing Regulation (EU) 2024/2690, Annex point 1.1: Policy on the security of network and information systems
- NIST PL-1: NIST SP 800-53 Rev. 5 PL-1: Policy and Procedures
- High
No security policy documentation found
NIS2 requires documented cybersecurity governance and risk management
What to do: Create and publish cybersecurity policy and framework documentation
- NIS2 21(2)(a)
- IR 2024/2690 1.1: Implementing Regulation (EU) 2024/2690, Annex point 1.1: Policy on the security of network and information systems
- NIST PL-1: NIST SP 800-53 Rev. 5 PL-1: Policy and Procedures
- High
No incident response procedures found
NIS2 requires documented incident response and business continuity plans
What to do: Implement and document incident response and business continuity procedures
- NIS2 21(2)(b)
- IR 2024/2690 3.1: Implementing Regulation (EU) 2024/2690, Annex point 3.1: Incident handling policy
- NIST IR-8: NIST SP 800-53 Rev. 5 IR-8: Incident Response Plan
- High
No security contact information
NIS2 requires clear incident reporting channels
What to do: Add security contact information (e.g., security@domain.com)
- RFC 9116 §2.5.3
- NIS2 21(2)(b)
- IR 2024/2690 3.3: Implementing Regulation (EU) 2024/2690, Annex point 3.3: Event reporting
- High
Critical sector without clear security compliance
Detected sectors: energy, transport, banking, health, digital
What to do: Critical sectors require comprehensive NIS2 compliance program
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching flock.io
This scan found 34 issues across 7 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
- Risk score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly. Cancel anytime. The full timeline opens with your unlock code.
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. Payments by EveryPay; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
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 comprehensive privacy and cookie policies with clear GDPR compliance statements.
- Add and configure essential security headers including CSP, HSTS, and X-Frame-Options.
- Publish clear contact information and establish incident response channels for security issues.
- Provide a vulnerability disclosure policy and security.txt file to improve transparency.
- Enhance WHOIS data transparency or provide justification for privacy protection to build trust.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- FLock
- Description
- FLock.io aims to build a decentralised privacy-preserving solution for Artificial Intelligence.
- Key services
- Federated machine learning platform, Blockchain integration for AI, Live AI models hosting, Training AI models on platform
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- React, Next.js, Ant Design, JavaScript
- Frameworks
- Next.js
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 50/100
Analytics and tracking
- Services
- Google Tag Manager
- Tracking level
- minimal
- Privacy compliance
- poor
Advertising
- Transparency
- poor
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- moderate
Key observations
- Website is fully accessible with no blocking or WAF challenge
- WHOIS data is not publicly available, indicating privacy protection
- No explicit privacy, cookie, or terms of service pages found
- No contact emails or phone numbers explicitly provided
- Website uses modern web technologies and frameworks
- Content is focused on decentralized AI and federated learning
- No security.txt or vulnerability disclosure found
- No security headers detected in provided data
- No advertising or tracking networks detected except Google Tag Manager
- No adult or questionable content detected
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.
- 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 and IETF Datatracker (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
Retrieved 2026-10-24
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 flock.io. Every review is verified by email and published after moderation.
Community rating
Loading reviews…