Skip to main content

Security report for csob.cz

Finance · Czech Republic

High risk. 8 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

The website csob.cz represents a mature financial institution based in the Czech Republic, with a domain age of 28 years indicating a well-established presence. However, the accessible website content is minimal and appears to be blocked by a web application firewall or security mechanism, limiting the ability to fully assess the site's offerings and user experience. The technical infrastructure includes Akamai DNS services, suggesting enterprise-grade hosting and CDN usage. Security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS support, which is critical for a financial services website. The site lacks visible privacy, cookie, or terms of service policies in the accessible content, raising compliance concerns. Overall, the website's security and privacy compliance require urgent improvement to meet industry standards and user trust expectations.

Scanned

This is an earlier scan of csob.cz. View the latest report

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

  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 csob.cz

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
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

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 csob.cz, from OffSeq Breach.

Total records
26,144
Employees
2
Customers
25,840
Third parties
302
Weak passwords
30%

Latest record dated 2025-12-13 · 146 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 csob.cz.

Select it in the checkout above.

Masked preview

  • –scube12a.intranet.csob.cz2025-12-13
  • –zameshop.csob.cz2025-07-20

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

CSOB is positioned as a key player in the finance sector in the Czech Republic, likely offering banking and financial services. The domain's maturity and DNS setup indicate a significant operational scale and reliance on robust infrastructure providers like Akamai. The lack of accessible content and contact information limits insights into customer engagement strategies, digital marketing, or partnership ecosystems. The business model is presumably traditional banking with digital service channels, but this cannot be confirmed from the current accessible data. The absence of visible certifications or trust indicators on the accessible site content is a gap that should be addressed to enhance credibility.

Security posture

The current security posture is weak, primarily due to the lack of a valid SSL certificate and no support for modern TLS protocols, which is a critical vulnerability for any financial institution. While some security headers are present, they are insufficient, and HSTS is not properly enabled. The presence of JavaScript-based bot mitigation suggests some level of security awareness, but the overall configuration exposes the site to risks such as data interception and user distrust. No vulnerability disclosure or incident response information is available, indicating potential gaps in security governance and transparency. Compliance with GDPR and other data protection regulations cannot be verified due to missing policy documents.

Recommendations

  1. Immediately install and maintain a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Enable and configure modern TLS protocols (TLS 1.2 and TLS 1.3) and strong cipher suites.
  3. Properly configure and enable HSTS with includeSubDomains and preload options to enforce HTTPS.
  4. Publish comprehensive privacy, cookie, and terms of service policies to demonstrate compliance.
  5. Implement and publicize a vulnerability disclosure policy and incident response contact channels.
  6. Improve website content accessibility by adjusting WAF/security settings to allow legitimate user access.
  7. Enhance website design and content quality to improve user experience and trustworthiness.
  8. Add clear contact information including emails, phone numbers, and physical addresses.
  9. Conduct regular security audits and penetration testing to identify and remediate vulnerabilities.
  10. Consider adding security certifications and trust seals to improve business credibility.
Technical notes

Notes

The website uses JavaScript and is hosted behind Akamai DNS services, indicating a reliance on CDN and security providers for performance and protection. However, the lack of a valid SSL certificate and absence of TLS protocol support severely undermine the site's security and user trust. The HTML content is minimal and primarily consists of obfuscated JavaScript likely used for bot mitigation, which also blocks content access. No CMS or frameworks are detectable from the accessible content. Performance metrics are unavailable due to blocked content, but the presence of Akamai suggests potential for good performance if properly configured. The site lacks SEO and accessibility features, and mobile optimization cannot be assessed due to content blocking. Overall, the technical implementation requires significant modernization and security hardening.
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

Earlier scans of this domain

  1. 60/100Medium33 findingsView report
Reviews of this site

Share your experience with csob.cz. 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 csob.cz.

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.