Skip to main content

Security report for walserprivatbank.com

Alpen Privatbank AG · Finance · Austria

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

Security score

33/100

Risk levelHigh

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

Alpen Privatbank AG is a well-established private banking and wealth management institution operating primarily in the German-speaking regions of Europe, with a strong presence in Austria and Germany. The company offers personalized asset management and investment advisory services, targeting private clients seeking tailored financial solutions. The website reflects a professional and consistent brand image, supported by multiple physical office locations and clear contact information. Technically, the site is built on TYPO3 CMS and hosted by maxcluster.net, but suffers from slow load times and lacks a valid SSL certificate, which significantly impacts security and user trust. The security posture is weak due to the absence of HTTPS and security headers, although privacy compliance is supported by a cookie consent mechanism and GDPR-aligned privacy policy. Overall, the site demonstrates moderate business credibility 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

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

  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 walserprivatbank.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
80
Network security
20
GDPR outside view
18
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

Technical appendix

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

Business context

Business profile

The Alpen Privatbank operates in the finance sector, focusing on private banking and wealth management services. Its market positioning as a reputable asset manager in the German-speaking market is supported by a mature domain and consistent branding. The business model revolves around personalized financial advisory and asset management, with digital services such as online banking accessible via a dedicated subdomain. The company maintains a multi-location presence, enhancing client proximity and service reach. The website content is relevant and professionally presented, targeting affluent private clients. The lack of visible certifications or security policies on the site suggests room for improvement in demonstrating compliance and trustworthiness. The partnership ecosystem includes links to financial reference sites and whistleblowing platforms, indicating regulatory awareness.

Security posture

The website's security posture is currently poor, primarily due to the absence of a valid SSL certificate and HTTPS support, exposing users to potential data interception risks. No security headers are implemented, and modern TLS protocols are not enabled, which further weakens the site's defense against common web attacks. The cookie consent mechanism is present, but no incident response or vulnerability disclosure policies are found, indicating limited preparedness for security incidents. The lack of OCSP stapling and session resumption features also impacts both security and performance. These vulnerabilities pose significant risks to user data confidentiality and the bank's reputation. Immediate remediation is recommended to align with industry best practices and regulatory requirements.

Recommendations

  1. Install and properly configure a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Implement essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  3. Enable HSTS with includeSubDomains and preload options to enforce secure connections.
  4. Establish and publish clear security policies, including incident response and vulnerability disclosure procedures.
  5. Optimize website performance to reduce load times, improving user experience and SEO.
  6. Enhance accessibility features to comply with standards and improve usability for all users.
  7. Regularly audit and update third-party scripts and libraries to avoid vulnerabilities.
  8. Consider adding visible certifications or trust seals to strengthen business credibility.

Contact details published on the site

Addresses
Legal name
Alpen Privatbank AG
Technical notes

Notes

The website is built on TYPO3 CMS, a mature and flexible content management system, hosted by maxcluster.net. The site uses JavaScript and integrates OneTrust for cookie consent management. Despite a professional design and good mobile optimization, the site suffers from slow loading times (over 20 seconds) and a large page size (~244 KB). SEO optimization is good with proper meta tags and structured data (JSON-LD) for organization information. However, the lack of HTTPS and security headers represents a critical technical debt. The DNS setup is stable with no DNSSEC enabled, and MX records point to a mail exchange server in Austria. The absence of modern TLS protocols and cipher suites indicates outdated or missing SSL configuration. Overall, the technical infrastructure supports the business but requires urgent security and performance improvements.
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 walserprivatbank.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 walserprivatbank.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.