Skip to main content

Security report for sonnenabo.at

SONNENABO · 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

SonnenAbo is a regional energy service provider based in Austria offering local solar power subscriptions through community photovoltaic parks. The business model focuses on enabling residents to access renewable energy without upfront investment, promoting sustainability and energy community membership. The website is professionally designed using modern web technologies such as Next.js and hosted on AWS infrastructure. However, the site lacks a valid SSL certificate and does not enforce HTTPS, which is a critical security vulnerability. Additionally, no cookie consent mechanism is present despite the use of Google Tag Manager, indicating partial privacy compliance. Contact information is available primarily as a physical address and contact page, but no direct emails or phone numbers are exposed. Overall, the website demonstrates moderate digital maturity but requires urgent security improvements to protect user data and enhance trust.

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 sonnenabo.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 company positions itself as a community-focused renewable energy provider targeting local residents interested in sustainable and affordable solar energy. Its competitive advantage lies in offering zero-investment solar subscriptions linked to local photovoltaic parks, supported by Burgenland Energie as a service provider. The business model is subscription-based with a focus on energy communities, which aligns with current trends in decentralized renewable energy. The website content is clear and relevant, targeting Austrian communities, but lacks detailed corporate information such as founding year or parent company. The partnership with Burgenland Energie is evident through asset hosting and branding. Growth potential depends on expanding community participation and municipal engagement.

Security posture

The website's security posture is weak due to the absence of HTTPS and TLS protocols, exposing users to potential data interception risks. The lack of security headers such as Content-Security-Policy and HSTS further increases vulnerability to common web attacks. Although AWS KMS encryption is used for S3 bucket storage, this does not compensate for the missing transport layer security. No incident response or vulnerability disclosure information is provided, limiting transparency. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. The use of Google Tag Manager introduces tracking without explicit user consent. Immediate remediation of SSL/TLS and security headers is recommended to improve security maturity.

Recommendations

  1. Implement and enforce HTTPS by installing a valid SSL/TLS certificate.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable insecure protocols.
  3. Add security headers including Content-Security-Policy, X-Frame-Options, X-XSS-Protection, and HSTS with preload.
  4. Introduce a cookie consent banner/mechanism to comply with GDPR and inform users about tracking.
  5. Publish a vulnerability disclosure policy or security.txt to improve transparency and incident response readiness.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built on a modern React/Next.js framework hosted on AWS infrastructure, leveraging Amazon S3 and CloudFront for content delivery. Google Tag Manager is used for analytics and marketing tracking. The site is mobile optimized with responsive design and good navigation clarity. However, performance metrics are missing or zero, indicating potential measurement gaps. Accessibility features are basic but present. The absence of HTTPS and security headers represents a significant technical debt and risk. SEO is basic with meta descriptions but no Open Graph or JSON-LD structured data detected. Overall, the technical stack is modern but requires security and privacy enhancements 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 sonnenabo.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 sonnenabo.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.