Skip to main content

Security report for swimsol.com

Swimsol GmbH · Energy · Austria

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

Security score

35/100

Risk levelHigh

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

Swimsol GmbH is a specialized energy company focused on providing floating and rooftop solar photovoltaic (PV) systems primarily for island environments such as the Maldives. The company positions itself as a leader in solar-at-sea technology with over 35 islands operating their systems and a significant installed capacity. Their business model includes system design, installation, operation, maintenance, and financing options, targeting luxury resorts and small businesses in tropical regions. Technically, the website is built on WordPress with a modern tech stack including Fusion Builder and WP Rocket, but lacks a valid SSL certificate, which impacts security and user trust. The site is well-designed, mobile-optimized, and SEO-friendly, with comprehensive content and strong branding. However, the absence of HTTPS and security headers represents a critical security gap. Privacy compliance is addressed with visible policies and consent mechanisms. Overall, Swimsol demonstrates a strong market presence and professional online representation but should prioritize securing their website with HTTPS and enhanced security practices.

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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 swimsol.com

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
40
GDPR outside view
18
Average
35

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

Swimsol holds a strong market position as the largest solar provider in the Maldives, leveraging over a decade of R&D and operational experience. Their competitive advantage lies in their unique floating solar solutions optimized for small islands, combined with comprehensive service offerings from design to maintenance. The company targets high-end hospitality and island communities, offering cost-saving and eco-friendly alternatives to diesel power. Their business model includes direct sales and financing options, enabling broader adoption. The company maintains a robust partnership ecosystem and a professional team exceeding 100 members. Their digital presence supports their business goals with detailed project showcases and social media engagement.

Security posture

The current security posture of the website is weak due to the lack of a valid SSL certificate and absence of critical security headers such as HSTS and CSP. While no known vulnerabilities or malware were detected, the site is served over HTTP only, exposing users to potential interception risks. The site does not implement advanced security policies or incident response information publicly. Privacy policies and cookie consent mechanisms are in place, indicating some compliance awareness. To improve, Swimsol should immediately deploy HTTPS, enable security headers, and consider publishing security and incident response policies to enhance trust and compliance.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish a dedicated security policy and incident response contact information.
  5. Regularly audit and update all server software and third-party libraries to mitigate vulnerabilities.

Contact details published on the site

Addresses
Legal name
Swimsol GmbH
VAT number
ATU 6708 0669
Registration number
375384k
Technical notes

Notes

The website is built on a WordPress CMS platform using the Avada theme and Fusion Builder framework, supported by various JavaScript libraries including jQuery, Bootstrap, and WP Rocket for performance optimization. The hosting provider is identified as my-webspace.at. Despite the use of modern technologies and SEO plugins like Yoast, the site lacks a valid SSL certificate and has no TLS protocols enabled, which is a significant technical deficiency. Performance metrics are not available or zero, suggesting potential issues with measurement or caching. The site is mobile-optimized with responsive design and accessibility features are basic but present. Overall, the technical infrastructure is solid but requires urgent security upgrades.
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 swimsol.com. 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 swimsol.com.

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.