Skip to main content

Security report for citadele.lv

Citadele · Finance · Latvia

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

Security score

65/100

Risk levelMedium

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

Citadele is a major Latvian banking institution offering a wide range of financial services including retail banking, loans, investments, insurance, and digital banking solutions. The website targets private individuals, businesses, and private banking clients, providing comprehensive tools such as loan calculators and digital onboarding. The company is part of the CBL Group and operates subsidiaries in Lithuania and Estonia. The website is professionally designed with excellent content quality and user experience, supporting multiple languages and accessibility features. Technically, the site uses OctoberCMS with jQuery, Bootstrap, and Slick Slider, but suffers from critical SSL/TLS misconfigurations that undermine security. Despite strong privacy and cookie consent mechanisms, the lack of a valid SSL certificate and modern TLS protocols poses significant risks. WHOIS data confirms domain legitimacy but highlights the absence of domain protection locks. Overall, the site is trustworthy and business credible but urgently needs to address its SSL/TLS security posture.

Scanned

This is an earlier scan of citadele.lv. 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

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

    • 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

    • 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

  2. 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 citadele.lv

This scan found 20 issues across 5 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
100
Security headers
30
Email security
87
DNS health
70
Network security
100
GDPR outside view
0
Average
65

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 citadele.lv, from OffSeq Breach.

Total records
4,729
Employees
6
Customers
4,704
Third parties
19
Weak passwords
28%

Latest record dated 2026-05-11 · 23 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 citadele.lv.

Select it in the checkout above.

Masked preview

  • –login.citadele.lv2026-05-11
  • –login.citadele.lv2025-07-28
  • –login.citadele.lv2025-07-20
  • –login.citadele.lv2025-07-08
  • –login.citadele.lv2025-04-15

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)

Brand lookalikes

Add-on

Domains that imitate citadele.lv and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
4
Registered
4
Resolving
4
High or critical
0

Last checked 2026-06-19

Masked preview

  • ci•••••.lvMediumomission
  • ci••••••.lvLowhomoglyph
  • ci•••.adele.lvLowsubdomain

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of citadele.lv with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

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

Citadele holds a strong market position in the Baltic banking sector with a focus on digital transformation and customer-centric services. Its business model revolves around providing comprehensive financial products to individuals and businesses, leveraging digital channels for onboarding and service delivery. The presence of multiple loan calculators and investment options indicates a diversified revenue stream. The company maintains active social media engagement and transparent privacy practices, enhancing customer trust. Partnerships and subsidiaries extend its regional footprint. Growth indicators include recent press releases and active content updates. The strategic emphasis on digital banking and customer self-service aligns with modern banking trends.

Security posture

The website's security maturity is moderate but compromised by critical issues. While it employs security best practices such as HSTS, HttpOnly and SameSite cookies, and GDPR-compliant privacy policies, the absence of a valid SSL certificate and disabled TLS protocols expose users to potential interception and man-in-the-middle attacks. The lack of DNSSEC and domain protection locks further weakens domain security. No explicit incident response or vulnerability disclosure policies are publicly available, indicating gaps in security governance. The site uses Google Tag Manager for analytics, which is standard but requires careful configuration to avoid privacy leaks. Overall, the security posture requires urgent remediation to meet industry standards and protect customer data.

Recommendations

  1. Immediately install and maintain a valid SSL/TLS certificate to enable HTTPS and secure user communications.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated protocols to enhance encryption strength.
  3. Implement DNSSEC and CAA records to protect DNS integrity and certificate issuance.
  4. Activate domain protection locks to prevent unauthorized domain transfers or modifications.
  5. Publish clear security policies including incident response and vulnerability disclosure to improve transparency and trust.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built on OctoberCMS and utilizes popular front-end libraries such as jQuery, Bootstrap, and Slick Slider for responsive design and interactive features. Google Tag Manager is integrated for analytics and marketing tracking. The site demonstrates good SEO practices with comprehensive meta tags, Open Graph data, and structured JSON-LD for organization and banking entity. Performance metrics indicate slow loading, possibly due to large page size or unoptimized resources. Accessibility features and mobile optimization are well implemented. However, the lack of SSL/TLS severely impacts the technical security posture and user trust. Hosting appears to be managed privately with dedicated DNS servers. Overall, the technical infrastructure supports a modern banking website but requires security upgrades and performance optimization.
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. 71/100Medium23 findings · partial scanView report
  2. 71/100Medium23 findings · partial scanView report
  3. 71/100Medium23 findings · partial scanView report
Reviews of this site

Share your experience with citadele.lv. 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 citadele.lv.

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.