Skip to main content

Security report for gutmann.at

Bank Gutmann · Finance · Austria

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

Security score

51/100

Risk levelMedium

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

Bank Gutmann is a well-established private banking institution based in Austria, specializing in wealth management, investment advice, and tailored investment solutions since 1922. The website reflects a professional and content-rich digital presence targeting private and institutional banking clients. The technical infrastructure is built on the Liferay CMS platform with modern JavaScript frameworks such as React and Clay UI, indicating a mature digital environment. However, the absence of a valid SSL certificate and HTTPS support significantly undermines the security posture of the website, exposing users to potential risks. Privacy and cookie policies are present and GDPR compliant, with a moderate level of user tracking via Piwik PRO analytics. Overall, the website demonstrates good business credibility and user experience but requires urgent security improvements to protect client data and maintain 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

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

This scan found 15 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
90
Network security
100
GDPR outside view
0
Average
51

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

Total records
13
Employees
0
Customers
8
Third parties
5
Weak passwords
38%

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

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

Bank Gutmann occupies a solid position in the Austrian private banking sector, offering a comprehensive suite of services including portfolio management, sustainable investment, and institutional banking solutions. The business model focuses on high-net-worth individuals and institutional clients, with a minimum investment threshold of EUR 500,000. The company leverages partnerships such as Gutmann KAG for fund management. The website's content and navigation are tailored to these audiences, providing clear service offerings and contact channels. The digital presence supports brand consistency and trust through professional design and social media engagement. Growth opportunities may include enhancing digital security and expanding transparency around certifications and incident response.

Security posture

The current security posture is weak due to the lack of HTTPS and SSL certificate, which is a critical vulnerability for any financial institution. While some security headers are implemented, the absence of TLS protocols and cipher suites, disabled HSTS, and no OCSP stapling indicate incomplete security hardening. No explicit security policies or incident response contacts are published, which could impact compliance with regulations such as GDPR and NIS2. The website uses secure cookie attributes and restrictive permissions policies, but these are insufficient without encrypted transport. Immediate remediation is required to install a valid SSL certificate and enable HTTPS to protect sensitive client interactions and data.

Recommendations

  1. Install and configure a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and strong cipher suites to secure communications.
  3. Activate and preload HSTS header to enforce HTTPS usage and prevent downgrade attacks.
  4. Publish a clear security policy and incident response contact information to enhance transparency and compliance.
  5. Conduct regular security audits and vulnerability assessments to identify and mitigate risks.
  6. Improve accessibility features and mobile optimization to enhance user experience.
  7. Expand trust indicators by displaying certifications and compliance badges where applicable.
Technical notes

Notes

The website is hosted on Apache server with DNS managed by a1.net, indicating a regional hosting provider. The CMS is Liferay, a robust enterprise platform, integrated with React and Clay UI for frontend components. The site uses modern JavaScript modules and includes AlloyEditor for content editing. Performance metrics indicate slow loading times, possibly due to missing resource size data or server-side delays. Mobile optimization is good, with responsive images and language switching capabilities. SEO is supported by proper meta tags and Open Graph data. However, the lack of HTTPS and SSL severely impacts the technical security posture. The site uses Piwik PRO for analytics, enabling moderate user tracking with privacy compliance. Overall, the technical stack is modern but requires security upgrades and performance tuning.
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 gutmann.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 gutmann.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.