Skip to main content

Security report for inbank.lv

Inbank · Finance · Latvia

Medium risk. 9 critical or high findings in GDPR outside view, Security headers and 2 other checks.

Security score

65/100

Risk levelMedium

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

Inbank is a Latvian financial institution focused on providing digital banking services such as loans and deposits to retail customers. The website is professionally designed and leverages modern web technologies including Nuxt.js and integration with Dokobit for secure digital authentication. The technical infrastructure appears solid with HTTPS enforced and use of reputable external libraries and APIs. However, the absence of explicit privacy and cookie policies, as well as lack of visible contact information and WHOIS data, limits the ability to fully assess compliance and legitimacy. Security posture is generally good but could be improved by implementing security headers and publishing incident response information. Overall, the website presents a credible banking service but would benefit from enhanced transparency and compliance documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 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

9 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 inbank.lv

This scan found 21 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. See sample alerts.

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
77
Security headers
55
Email security
80
DNS health
70
Network security
100
GDPR outside view
10
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 inbank.lv, from OffSeq Breach.

Total records
76
Employees
0
Customers
76
Third parties
0
Weak passwords
0%

3 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 inbank.lv.

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

Inbank operates in the banking sector with a digital-first approach targeting retail customers primarily in Latvia. The business model centers on online loan applications and account management, positioning itself as a modern alternative to traditional banks. The company appears to have a medium-sized market presence with consistent branding and trust signals such as secure authentication integration. The lack of detailed company registration and contact data on the website suggests an opportunity to improve customer trust and regulatory compliance visibility. No partner or subsidiary domains were identified in the analyzed content.

Security posture

The website enforces HTTPS and uses secure digital signature technologies via Dokobit, indicating a focus on secure customer interactions. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces defense-in-depth. No vulnerabilities or exposed sensitive data were detected in the provided content. The lack of published security policies, incident response contacts, or vulnerability disclosure mechanisms suggests limited transparency in security governance. Overall, the security maturity is moderate with room for improvement in policy publication and technical hardening.

Recommendations

  1. Implement and enforce security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements and consent mechanisms to improve legal compliance and user trust.
  3. Provide explicit contact information including support emails and phone numbers to facilitate customer communication and incident reporting.
  4. Establish and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Regularly monitor WHOIS data availability and ensure domain registration details are transparent and consistent with business claims.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Inbank
Description
Inbank is a financial institution providing banking services including loans and deposits primarily targeting retail customers.
Key services
Loans, Deposits, Digital banking
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.5.1, Google Maps API, Core-js polyfills
Frameworks
Nuxt.js (implied by _nuxt script paths)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Use of digital signature and authentication via Dokobit

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. WHOIS data unavailable due to query limit error
  3. Website uses HTTPS and modern JavaScript frameworks
  4. No explicit privacy, cookie, or terms of service pages detected in provided HTML
  5. No contact emails or phone numbers explicitly found in provided HTML snippet
  6. Integration with Dokobit indicates use of secure digital authentication
  7. No visible security.txt or vulnerability disclosure information
  8. No social media links explicitly found in provided HTML snippet
  9. No explicit security headers detected in provided data
  10. Website content is professional and consistent with banking sector
Technical notes

Notes

The website uses a modern JavaScript framework (Nuxt.js) with server-side rendering capabilities, enhancing SEO and performance. External libraries include jQuery 3.5.1, Google Maps API, and Dokobit authentication scripts, indicating integration with trusted third-party services. The site is mobile optimized with responsive design elements. Performance is moderate, with potential improvements in loading speed and accessibility features. No CMS was detected, suggesting a custom or framework-based implementation. Hosting provider details were not identifiable from the provided data.
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 inbank.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 inbank.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.