Skip to main content

Security report for sclable.com

Sclable Business Solutions GmbH · Technology · Austria

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

Security score

33/100

Risk levelHigh

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

Sclable Business Solutions GmbH is a Vienna-based digital innovation studio founded in 2012, specializing in custom software development, AI-driven digital solutions, and human-centered design. The company serves a diverse B2B clientele across industries such as manufacturing, IoT, healthcare, construction, mobility, financial services, and energy. With over 50 professionals and 120+ live projects, Sclable positions itself as a medium-sized, reputable player in the technology consulting and software development market. The website reflects a professional and consistent brand image with strong client endorsements and comprehensive service descriptions. Technically, the website runs on an Apache server with modern frontend libraries like Swiper and QR code generation scripts. While the site is mobile-optimized and accessible with good SEO practices, it lacks a valid SSL certificate and proper HTTPS configuration, which is a significant security shortfall. Performance metrics are missing, but inferred to be slow. No CMS or major frameworks are detected, indicating a custom-built site. From a security perspective, the site has minimal security headers and no active TLS protocols, exposing it to potential risks. The absence of DMARC, DNSSEC, and CAA records further weakens email and domain security. No incident response or vulnerability disclosure policies are present, limiting transparency in security management. However, privacy and cookie policies with consent mechanisms are well implemented, indicating good GDPR compliance. Overall, while the business and website demonstrate professionalism and trustworthiness, the lack of HTTPS and modern security configurations poses a critical risk. Strategic improvements in SSL deployment, email security, and incident response transparency are recommended to enhance the security posture and maintain client trust.

Scanned

NIS2 and GDPR posture

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

8 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

    • 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

  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 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 sclable.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
30
Email security
50
DNS health
75
Network security
40
GDPR outside view
0
Average
33

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention sclable.com, from OffSeq Breach.

Total records
3
Employees
0
Customers
3
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for sclable.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Sclable operates in a competitive digital innovation market, leveraging a hybrid business model combining consultancy, design, and technology development. Their client base includes prominent Austrian and European companies in transportation, manufacturing, finance, and healthcare, indicating strong market positioning and partnership networks. The company’s focus on AI and data-driven solutions aligns with current digital transformation trends, providing competitive advantages. Revenue streams likely derive from project-based custom software development and ongoing consulting services. The presence of testimonials and client logos enhances credibility and supports growth. The company’s medium size and Vienna location position it well for regional influence with potential for expansion.

Security posture

The current security maturity level is low due to the absence of HTTPS and modern TLS protocols, which is a critical vulnerability impacting data confidentiality and integrity. The lack of DMARC and DNSSEC exposes the domain to email spoofing and DNS attacks. No formal incident response or vulnerability disclosure mechanisms are in place, limiting preparedness for security incidents. Privacy compliance is strong with clear policies and consent mechanisms, but technical security gaps undermine overall risk management. The business impact of these vulnerabilities includes potential data breaches, loss of client trust, and regulatory non-compliance risks. Enhancing SSL/TLS, implementing email security standards, and establishing incident response processes are essential to improve security culture and resilience.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire website immediately.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable insecure protocols to protect data in transit.
  3. Implement DMARC, SPF, and DKIM records to secure email communications and prevent spoofing.
  4. Establish a security.txt file and publicly document incident response contacts and procedures.
  5. Enable DNSSEC and CAA records to strengthen domain name system security and certificate issuance control.

Contact details published on the site

Addresses
Legal name
Sclable Business Solutions GmbH
Technical notes

Notes

The website is hosted on an Apache server with a custom-built frontend using Swiper JS for sliders and a QR code library. Fonts are preloaded for performance, and CSS is modularized. However, the lack of HTTPS and TLS support is a major technical deficiency. Performance data is missing, but the zero loadTime and resourceCount suggest incomplete metrics or slow loading. The site is mobile-optimized and accessible with semantic HTML and ARIA attributes. SEO is supported by proper meta tags and Open Graph data. No CMS or backend frameworks are detected, indicating a bespoke solution. Hosting provider details are not explicit but IP address suggests a dedicated or VPS environment. Technical debt includes missing security configurations and lack of automated security headers.
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 sclable.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 sclable.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.