Skip to main content

Security report for fcbe.at

Fanclub Burgenland Energieunabhängig · Energy · Austria

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

45/100

Risk levelHigh

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

Fanclub Burgenland Energieunabhängig is a regional energy community initiative based in Burgenland, Austria, focused on promoting renewable energy usage through wind and solar power. The organization offers membership benefits including access to renewable energy at attractive prices, participation in regional energy projects, and digital services to support energy independence. The website is well-designed, content-rich, and targets residents, businesses, and municipalities interested in sustainable energy solutions. Technically, the site uses modern web frameworks such as Next.js and is hosted on AWS infrastructure, but suffers from a critical security shortfall due to the absence of a valid SSL certificate and HTTPS support. Privacy compliance is strong with a comprehensive GDPR-aligned privacy policy and explicit data processing consents in forms. Contact information is clearly provided, enhancing business credibility. However, the lack of cookie consent mechanisms and security headers reduces the overall security posture. Strategic improvements in SSL deployment and security best practices are recommended to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

  2. 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

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

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

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

Keep watching fcbe.at

This scan found 19 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
0
Security headers
15
Email security
50
DNS health
85
Network security
100
GDPR outside view
18
Average
45

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 is positioned as a key regional player in the renewable energy sector in Burgenland, Austria, leveraging partnerships with Burgenland Energie and other local entities. Its community-based business model focuses on energy independence and sustainability, targeting private customers, businesses, and municipalities. The website supports lead generation through detailed forms and provides extensive information about energy projects and benefits. The partnership ecosystem is strong, with clear links to energy consulting and solar subscription services. Growth potential is indicated by plans for expanding regional energy communities. The business model relies on membership fees and energy supply benefits, emphasizing long-term stability and regional energy autonomy.

Security posture

The current security posture is weak due to the lack of a valid SSL certificate and HTTPS, exposing users to potential data interception risks. No modern TLS protocols or HSTS are enabled, and OCSP stapling and session resumption are absent. While server-side encryption is used for content storage on AWS, the website delivery lacks essential transport security. Forms collect sensitive personal data with explicit consent, but the absence of HTTPS undermines data protection. No incident response or security policy pages are found, and no vulnerability disclosure or security.txt files are present. Immediate remediation of SSL/TLS issues is critical to protect user data and comply with security standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and configure HSTS with includeSubDomains and preload directives.
  3. Implement OCSP stapling and session resumption to improve SSL performance and security.
  4. Add a cookie consent banner/mechanism to comply with privacy regulations and inform users about tracking.
  5. Publish a security policy and incident response contact information to enhance transparency and trust.
  6. Conduct regular security audits and vulnerability scans to identify and fix potential issues.
  7. Enhance security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built using Next.js, a React-based framework, and hosted on AWS S3 with CloudFront CDN, ensuring scalability and global delivery. Google Tag Manager is used for analytics and marketing tracking. The site is mobile optimized and accessible with good SEO practices. However, performance metrics are missing or zero, indicating potential monitoring gaps. The absence of HTTPS is a major technical flaw. The site uses modern JavaScript chunking and lazy loading for resources, indicating a modern frontend architecture. The DNS setup uses AWS DNS servers with multiple A records for redundancy. Overall, the technical infrastructure is modern but requires urgent security upgrades to meet best practices.
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 fcbe.at. 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 fcbe.at.

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.