Skip to main content

Security report for hyponoe.at

HYPO NOE Landesbank für Niederösterreich und Wien AG · Finance · Austria

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

Security score

44/100

Risk levelHigh

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

HYPO NOE Landesbank für Niederösterreich und Wien AG is a well-established regional financial institution in Austria, offering a broad range of banking services including retail accounts, savings, investments, financing, and green banking products. The website targets private customers, young adults, companies, and public sector entities, emphasizing sustainability and digital banking solutions. Technically, the site is built on TYPO3 CMS with modern frontend technologies and includes cookie consent management and analytics integration. However, the security posture is weakened by the absence of a valid SSL certificate and lack of TLS support, which is critical for a banking website. Despite this, the site maintains good privacy compliance and business credibility with clear contact information and certifications. Strategic improvements in SSL/TLS configuration and security headers are recommended to enhance trust and 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 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 hyponoe.at

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
85
Network security
100
GDPR outside view
0
Average
44

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 bank holds a strong market position in Lower Austria and Vienna, focusing on sustainable finance and digital services. Its business model integrates traditional banking with modern online and mobile payment solutions. The presence of green financial products and sustainability certifications indicates a competitive advantage in eco-conscious banking. The company maintains active social media channels and partnerships, including with arz.at for mail and DNS services. The website content is professionally curated, targeting diverse customer segments with tailored offerings. Growth potential lies in expanding digital services and reinforcing security to meet regulatory standards.

Security posture

The current security maturity is low due to the lack of HTTPS and TLS protocols, exposing users to potential data interception risks. While some security headers like HSTS are present, critical elements such as valid SSL certificates, strong cipher suites, OCSP stapling, and session resumption are missing. No explicit security or incident response policies are found on the site. The absence of vulnerability disclosure mechanisms and security.txt files limits transparency. Compliance with GDPR is supported by privacy and cookie policies, but technical security gaps pose significant risks for a financial institution. Immediate remediation of SSL/TLS issues is essential to protect customer data and maintain regulatory compliance.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and configure strong cipher suites.
  3. Implement additional security headers such as Content-Security-Policy and X-Frame-Options.
  4. Establish and publish a security policy and incident response contact information.
  5. Introduce a vulnerability disclosure program or security.txt file to enhance transparency.
Technical notes

Notes

The website uses TYPO3 CMS with Bootstrap and jQuery for frontend responsiveness and interactivity. Lazy loading of images is implemented via lazysizes, improving perceived performance. Cookiebot manages cookie consent, ensuring privacy compliance. Google Tag Manager and Google Ads are integrated for analytics and marketing. Despite modern frontend technologies, the site lacks SSL/TLS security, which is a critical technical debt. Performance metrics are missing, but the presence of multiple large images and scripts suggests moderate loading speed. Accessibility and SEO optimizations are good, with proper meta tags and ARIA attributes. Hosting provider details are not explicit but DNS and MX records point to arz.at 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 hyponoe.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 hyponoe.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.