Skip to main content

Security report for finstar.ch

Finstar AG · Finance · Switzerland

Medium risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

74/100

Risk levelMedium

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

Finstar AG is a Swiss-based company specializing in integrated IT solutions for private and universal banks as well as fintechs. With over 40 years of experience, the company offers customized and cost-effective banking software and services, positioning itself as a trusted partner in the financial technology sector. Their offerings include a broad range of products and services such as APIs, digital onboarding, and digital asset platforms, supported by a strong ecosystem of partner banks and financial institutions. The company is a subsidiary of Hypothekarbank Lenzburg AG and holds the prestigious 'swiss made software' label, underscoring its commitment to quality and reliability. Technically, the website is built on the Umbraco CMS and leverages modern JavaScript libraries including GSAP and ScrollMagic for enhanced user experience. It integrates Cookiebot for GDPR-compliant cookie consent management and Google Tag Manager for analytics and marketing. However, the website currently lacks a valid SSL certificate and does not support modern TLS protocols, which is a critical security gap. Performance is slow, likely due to the large page size and resource count, but mobile optimization and accessibility are rated good. From a security perspective, the domain has well-configured SPF and DMARC records with a strict reject policy, reducing email spoofing risks. Despite this, the absence of HTTPS and security headers significantly lowers the security posture. No explicit security policy, incident response contacts, or vulnerability disclosure mechanisms were found. The cookie consent mechanism is comprehensive and transparent, supporting GDPR compliance. Overall, Finstar AG presents a professional and trustworthy digital presence with strong business credentials and compliance in privacy and cookie management. The primary risk lies in the lack of HTTPS, which should be addressed urgently to protect user data and maintain trust. Strategic improvements in security infrastructure and transparency around security policies would enhance the company's risk profile and customer confidence.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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

4 findings rated critical or high. Fix these first.

  1. 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching finstar.ch

This scan found 18 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
75
Security headers
45
Email security
95
DNS health
85
Network security
100
GDPR outside view
43
Average
74

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 finstar.ch, from OffSeq Breach.

No leaked records found

Breach holds no records for finstar.ch right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

Finstar AG operates in the niche market of banking IT solutions, targeting private and universal banks and fintech companies. Their business model is B2B, providing software and IT services tailored to the financial sector. The company leverages a strong partnership ecosystem, including its parent company Hypothekarbank Lenzburg AG and multiple customer banks showcased on the website. The swiss made software label and multiple awards indicate a competitive advantage based on quality and reliability. Revenue streams likely include software licensing, SaaS/PaaS offerings, consulting, and migration services. The presence of a multilingual website and extensive content suggests a focus on international and Swiss markets. Growth indicators include a partner network of over 50 entities and a medium-sized employee base. The company emphasizes innovation and customer-centric solutions, positioning itself as a forward-looking player in the fintech ecosystem.

Security posture

The current security maturity of Finstar AG's web presence is moderate with significant room for improvement. The domain benefits from correctly configured SPF and DMARC DNS records with a reject policy, which helps mitigate email spoofing and phishing risks. However, the lack of a valid SSL certificate and absence of HTTPS support is a critical vulnerability that exposes users to data interception and undermines trust. No security headers such as Content-Security-Policy or X-Frame-Options are detected, increasing the risk of common web attacks. The cookie consent implementation is robust and GDPR compliant, reflecting good privacy practices. No public security policy, incident response contacts, or vulnerability disclosure channels were found, indicating a gap in transparency and readiness for security incidents. Overall, while email security is strong, web security practices need urgent enhancement to align with industry standards and regulatory requirements.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and disable all insecure protocols to protect data in transit.
  3. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  4. Publish a clear security policy and incident response information, including dedicated contact channels for security issues.
  5. Establish and publish a vulnerability disclosure program, including a security.txt file, to encourage responsible reporting and improve security posture.
Technical notes

Notes

The website is built on the Umbraco CMS platform and uses a variety of modern JavaScript libraries including GSAP for animations, ScrollMagic for scroll-based effects, and Photoswipe for image galleries. Cookiebot is integrated for cookie consent management, and Google Tag Manager is used for analytics and marketing tags. The hosting provider is ip-plus.net, with DNS managed by ns1.ip-plus.net and ns2.ip-plus.net. Performance metrics indicate a slow load time (18+ seconds) and a large page size (~473 KB) with 139 resources, suggesting optimization opportunities. Mobile optimization and accessibility are rated good, with responsive design and language options for English, German, and French. SEO is supported by structured data (JSON-LD) for organization and website schema, as well as Open Graph and Twitter card metadata. The lack of HTTPS and modern TLS support is a significant technical risk. Overall, the infrastructure is modern but requires security and performance improvements to reduce technical debt and enhance user experience.
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 finstar.ch. 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 finstar.ch.

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.