Skip to main content

Security report for flyo.cloud

Technology · N/a

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

70/100

Risk levelMedium

0–100, higher is better. How it is calculated

flyo.cloud is a technology-focused SaaS platform aimed at revolutionizing content workflows, targeting content creators and teams. The website presents a professional login page with modern design elements and uses technologies such as Vue.js, Font Awesome, and Google reCAPTCHA to enhance user experience and security. The domain is registered since 2021 and uses Cloudflare for DNS and hosting, indicating a reliable technical infrastructure. However, the site lacks visible privacy, cookie, and terms of service policies, which are critical for compliance and user trust. Security posture is moderate with HTTPS and bot protection but lacks security headers and published security policies. Overall, the website is functional and professional but would benefit from enhanced privacy compliance and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (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

5 findings rated critical or high. Fix these first.

  1. 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 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';…
  2. 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

  3. 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching flyo.cloud

This scan found 21 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
57
Security headers
65
Email security
60
DNS health
80
Network security
100
GDPR outside view
58
Average
70

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

The business operates in the technology sector with a SaaS model focused on content workflow management. The company appears to be small-sized and relatively new, founded around 2021. The website content is primarily in German, indicating a possible regional focus. There is no explicit information about parent companies or subsidiaries. The lack of contact information and policies on the login page suggests that these may be located elsewhere or not publicly disclosed. The company leverages Cloudflare services and modern web technologies, positioning itself as a contemporary digital service provider.

Security posture

The website enforces HTTPS and uses Google reCAPTCHA to mitigate automated abuse, which are positive security measures. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and others reduces the overall security posture. No incident response or vulnerability disclosure information is provided, limiting transparency in security management. The domain registration is consistent and transparent, with no privacy protection, which supports trustworthiness. To improve security maturity, the company should implement comprehensive security headers, publish security policies, and provide clear incident response contacts.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to enhance GDPR compliance.
  2. Add security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen security posture.
  3. Provide clear contact information including support and security incident response channels on the website.
  4. Establish and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are in use.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Revolutioniere deinen Content Workflow
Key services
content workflow revolution, content management
Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, Font Awesome, Google reCAPTCHA
Frameworks
Vue.js (implied by v-application classes)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Google reCAPTCHA used for bot protection

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
basic
Navigation
basic
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is accessible and not blocked by WAF or security challenges.
  2. No explicit privacy, cookie, or terms of service policies found on the login page.
  3. No contact emails, phone numbers, or physical addresses found in the provided content.
  4. Uses modern JavaScript frameworks and Google reCAPTCHA for security.
  5. Domain is registered with a reputable registrar and uses Cloudflare DNS.
  6. No evidence of security.txt or vulnerability disclosure policy.
  7. Content is in German language with a focus on content workflow revolution.
  8. No social media links or business certifications detected on the login page.
  9. No advertising or tracking scripts detected beyond Font Awesome and reCAPTCHA.
Technical notes

Notes

The website uses a modern JavaScript framework (likely Vue.js) and includes Font Awesome icons and Google reCAPTCHA for UI and security. Hosting and DNS are managed via Cloudflare, providing performance and security benefits. The site is moderately optimized for mobile and accessibility but lacks advanced SEO and accessibility features. No CMS is explicitly detected. Performance is moderate, with asynchronous loading of scripts. The absence of DNSSEC is a minor risk. Overall, the technical infrastructure is solid but could be enhanced with additional security and compliance features.
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.

Retrieved 2026-10-25

Reviews of this site

Share your experience with flyo.cloud. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review flyo.cloud.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.