Skip to main content

Security report for sabes.it

Südtiroler Sanitätsbetrieb · Healthcare · Italy

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

Security score

48/100

Risk levelHigh

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

Südtiroler Sanitätsbetrieb operates as a regional healthcare provider in South Tyrol, Italy, serving the local population with healthcare services. The website is primarily a digital presence for the organization but currently offers minimal direct content or user interaction features. The technical infrastructure is hosted on Microsoft Azure and uses JavaScript-based analytics and cookie consent tools. However, the site lacks a valid SSL certificate, resulting in no HTTPS support, which is a critical security deficiency. Security headers are implemented, but the absence of TLS protocols and HSTS reduces the overall security posture. Privacy compliance is limited, with no visible privacy or terms of service policies, though a cookie consent mechanism is present. WHOIS data confirms the domain is mature and legitimately registered, consistent with the organization's profile. Overall, the website requires significant improvements in security, privacy transparency, and content richness to better serve its audience and meet modern standards.

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

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

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

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

Keep watching sabes.it

This scan found 16 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
65
Email security
50
DNS health
75
Network security
100
GDPR outside view
0
Average
48

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 organization is positioned as a public healthcare entity with a stable market presence in the South Tyrol region. Its business model focuses on providing essential healthcare services to residents. The website's limited content and lack of direct contact information suggest it serves more as an informational portal rather than a full-service digital platform. The use of external analytics and marketing tools indicates some level of digital engagement, but the absence of comprehensive privacy policies and contact channels may hinder user trust and engagement. There is no evidence of commercial activities or partnerships beyond standard service providers for analytics and hosting.

Security posture

The current security posture is weak due to the lack of HTTPS and modern TLS protocols, exposing users to potential interception risks. While security headers like CSP, X-Frame-Options, and X-XSS-Protection are present, the absence of SSL/TLS and HSTS significantly undermines security. No incident response or vulnerability disclosure information is available, indicating limited transparency in security management. Cookie consent is implemented, but GDPR compliance cannot be fully verified without a privacy policy. The domain registration is consistent and trustworthy, but technical security improvements are urgently needed to protect user data and enhance trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and configure HSTS to enforce secure connections.
  3. Publish comprehensive privacy and terms of service policies to improve GDPR compliance and user trust.
  4. Add clear contact information including emails, phone numbers, and physical addresses to enhance transparency.
  5. Implement a formal vulnerability disclosure policy and incident response contact channels to improve security posture.
Technical notes

Notes

The website is hosted on Microsoft Azure and uses JavaScript for analytics (SiteImprove) and cookie consent (CookieIUB). The HTML content is minimal and relies on client-side scripts for dynamic content loading. No CMS or major frameworks are detected. Performance data is missing, but the lack of SSL and modern protocols suggests technical debt and potential risks. External dependencies are numerous, including fonts, analytics, and marketing services. Accessibility and SEO optimizations appear basic, with minimal metadata and no structured data present. The site would benefit from modernization efforts including improved security configurations, enhanced content delivery, and better compliance with web standards.
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 sabes.it. 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 sabes.it.

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.