Skip to main content

Security report for theflywheel.app

Other · N/a

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

Security score

68/100

Risk levelMedium

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

Theflywheel.app's landing page at /lander is currently a minimal placeholder or parking page with very limited content. The site primarily loads a JavaScript bundle and a CSS stylesheet from wsimg.com and includes a Google Adsense script, indicating monetization attempts but no substantive business content or user engagement features. There are no visible privacy, cookie, or terms of service policies, nor any contact information or social media links. The lack of content and metadata suggests the site is either under development or not actively maintained. From a technical perspective, the site uses basic JavaScript and CSS assets but lacks modern SEO, accessibility, and performance optimizations. No CMS or frameworks are detected beyond the static assets. The absence of HTTPS or security headers in the provided data raises concerns about security posture. No forms or data collection mechanisms are present, limiting privacy compliance considerations. Security evaluation indicates a poor posture due to missing HTTPS, lack of security headers, and no visible incident response or vulnerability disclosure information. The site does not provide any trust or compliance signals, which negatively impacts its credibility and user trust. Overall, theflywheel.app's landing page is not currently suitable for business or user engagement and requires significant improvements in content, security, compliance, and technical implementation to be considered a professional and trustworthy website.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

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

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 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

    • 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

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

Keep watching theflywheel.app

This scan found 22 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. 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. 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
77
Security headers
25
Email security
75
DNS health
80
Network security
100
GDPR outside view
50
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

Due to the minimal content and lack of business information on the landing page, no meaningful business intelligence can be derived. There is no indication of company name, services, market positioning, or target audience. The presence of Google Adsense suggests a possible advertising revenue model, but no direct business model or customer segments are identifiable. No partnerships or subsidiaries are referenced. The domain appears to be underutilized or parked.

Security posture

The security posture of theflywheel.app is currently weak. The absence of HTTPS or SSL data is a critical issue, exposing users to potential interception risks. No security headers are detected, and there is no evidence of secure coding practices or vulnerability management. The lack of privacy and cookie policies indicates non-compliance with GDPR and other data protection regulations. No incident response or vulnerability disclosure mechanisms are provided, limiting the ability to handle security incidents effectively. Overall, the site does not demonstrate a mature security culture or readiness.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure user connections.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and inform users.
  3. Provide clear contact information including email and phone for business and security inquiries.
  4. Incorporate security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Develop substantive website content to improve user engagement, SEO, and trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
moderate

Technology

Stack
JavaScript
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Google Adsense
Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is minimal and appears to be a placeholder or parking page.
  2. No visible privacy, cookie, or terms of service policies.
  3. No contact information or business details provided on the page.
  4. Only external scripts are from Google Adsense and wsimg.com hosting static assets.
  5. No forms or user input fields detected.
  6. No social media links or email addresses found.
  7. No security headers or SSL configuration details available from provided data.
  8. No structured data (JSON-LD) or Open Graph metadata present.
  9. Website appears to be a parked domain or under construction.
Technical notes

Notes

The website uses basic JavaScript and CSS assets loaded from wsimg.com and includes Google Adsense scripts for advertising. There is no evidence of a CMS or advanced frameworks. The site lacks meta tags, structured data, and SEO optimizations. Performance is likely moderate due to minimal content but could be improved with better optimization. Mobile optimization and accessibility are basic at best. The absence of security headers and HTTPS data indicates technical debt in security implementation. Overall, the technical infrastructure is minimal and requires modernization to support a professional web presence.
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 theflywheel.app. 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 theflywheel.app.

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.