Skip to main content

Security report for stanna.at

St. Anna Kinderspital · Healthcare · Austria

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

Security score

38/100

Risk levelHigh

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

St. Anna Kinderspital is a well-established pediatric hospital located in Vienna, Austria, providing comprehensive medical care for children and adolescents. The website reflects a strong commitment to patient care and family support, offering detailed information about medical departments, services, and patient guidance. The institution operates as a non-profit entity supported by donations, with clear calls to action for donations and career opportunities. Technically, the website is built on WordPress with modern plugins for SEO, multilingual support, and cookie management, but lacks HTTPS which is a critical security shortfall. Security headers are partially implemented, but the absence of SSL/TLS and modern TLS protocols significantly weakens the security posture. Privacy compliance is well addressed with a comprehensive privacy policy and cookie consent mechanism. Overall, the site is professional and trustworthy but urgently needs to implement HTTPS to protect user data and improve security.

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

  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 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 stanna.at

This scan found 17 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
50
Email security
50
DNS health
85
Network security
40
GDPR outside view
0
Average
38

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 stanna.at, from OffSeq Breach.

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

2 subdomains 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 stanna.at.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

The hospital holds a strong market position in pediatric healthcare in Austria, targeting children, adolescents, and their families. Its business model is focused on healthcare service provision supported by public and private donations. The website content and structure indicate a mature digital presence with multilingual capabilities and active community engagement through news, stories, and donation campaigns. Partnerships with healthcare organizations and use of professional recruitment platforms like softgarden indicate a robust operational ecosystem. The institution's transparency in donation handling and clear contact information enhance its credibility and trustworthiness in the healthcare sector.

Security posture

The current security posture is weak due to the lack of HTTPS and modern TLS support, exposing users to potential data interception risks. While some security headers like X-Frame-Options, X-Content-Type-Options, and X-XSS-Protection are present, the absence of SSL/TLS and HSTS is a critical vulnerability. No incident response or vulnerability disclosure information is found, which could limit the hospital's ability to manage security incidents effectively. The cookie consent mechanism and privacy policy demonstrate good privacy practices, but the overall security framework requires urgent enhancement to meet modern standards and regulatory requirements.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Upgrade server configuration to support TLS 1.2 and TLS 1.3 protocols.
  4. Publish a security policy and incident response contact information to improve transparency and readiness.
  5. Regularly audit and update security headers and ensure all forms use secure submission methods.

Contact details published on the site

Addresses
Technical notes

Notes

The website is powered by WordPress CMS with a modern tech stack including Apache server, Yoast SEO for search optimization, WPML for multilingual support, and Borlabs Cookie for cookie management and GDPR compliance. JavaScript libraries such as jQuery and Swiper.js are used for interactive elements. Hosting is provided by NextLayer as indicated by DNS NS records. Performance metrics are not available, but the site is likely moderate to slow due to lack of performance data and chunked transfer encoding. Mobile optimization and accessibility are good, with responsive design and ARIA roles implemented. SEO is well handled with proper meta tags, Open Graph, and JSON-LD structured data. Technical debt is moderate, with a critical need to upgrade security infrastructure.
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 stanna.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 stanna.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.