Skip to main content

Security report for inbank.ee

Inbank AS · Finance · Estonia

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

Security score

68/100

Risk levelMedium

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

Inbank AS is a digital financial services provider based in Estonia, offering a variety of banking products such as unsecured loans, deposits, leasing, and payment solutions. The company targets both private individuals and merchants, emphasizing fully digital and flexible financing options. The website reflects a mature business with a decade of domain registration and a solid customer base exceeding 500,000 across Europe. Technically, the site uses modern frameworks like Nuxt.js and integrates third-party services such as Dokobit for authentication and Google reCAPTCHA for bot protection. However, the website suffers from critical security shortcomings, notably the absence of a valid SSL certificate and HTTPS support, which severely impacts its security posture. Privacy and cookie policies are present and indicate GDPR compliance, but no explicit security or incident response policies are found. Overall, while the business and content quality are good, the lack of proper SSL/TLS configuration and security headers significantly lowers the security score and poses risks to user trust and data protection.

Scanned

This is an earlier scan of inbank.ee. 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 inbank.ee

This scan found 18 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. 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
100
Security headers
55
Email security
85
DNS health
70
Network security
100
GDPR outside view
0
Average
68

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

Inbank operates in the competitive digital banking sector, leveraging a fully digital business model to provide loans, deposits, and leasing services. Its market positioning is strong within Estonia and expanding across Europe, supported by a robust online presence and investor relations. The company benefits from partnerships and developer portals, indicating an ecosystem approach. Revenue streams likely include interest from loans, leasing fees, and deposit products. The target customer segments include retail consumers seeking flexible financing and merchants requiring payment and financing solutions. Growth indicators include a mature domain, extensive customer base, and active recruitment efforts. Strategic observations suggest a focus on digital innovation and customer convenience, though technical and security improvements are needed to maintain competitive advantage.

Security posture

The current security maturity level of the website is low due to the absence of a valid SSL certificate and HTTPS support, which is a critical vulnerability for any financial institution. No security headers such as HSTS or Content-Security-Policy are implemented, and no OCSP stapling or session resumption mechanisms are enabled. While there are no detected vulnerabilities like Heartbleed or POODLE, the lack of encryption exposes users to potential data interception and undermines trust. Compliance gaps exist in the absence of explicit security and incident response policies on the website. Data protection practices are partially evidenced by GDPR-compliant privacy policies, but incident response readiness and security culture indicators are not visible. The business impact of these vulnerabilities is high, risking customer data confidentiality and regulatory compliance.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Implement essential security headers including HSTS, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable OCSP stapling and session resumption to improve security and performance.
  4. Publish clear security and incident response policies, including dedicated contact channels for security incidents.
  5. Conduct regular security audits and vulnerability assessments to identify and remediate risks proactively.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built using modern JavaScript frameworks, primarily Nuxt.js, and integrates several third-party services such as Dokobit for digital authentication and Google reCAPTCHA for bot mitigation. Hosting is provided via Amazon AWS, as indicated by the DNS nameservers. Despite the modern tech stack, the website suffers from slow load times and a very large page size (~50MB), which negatively impacts user experience and SEO. Mobile optimization is good, with responsive design elements present. Accessibility features are basic but present. SEO optimization is basic with standard meta tags but no advanced structured data like JSON-LD detected. Technical debt is evident in the lack of SSL and security headers, which are critical for a financial services website. Modernization opportunities include performance optimization, enhanced accessibility, and improved security configurations to reduce operational risks.
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. 69/100Medium28 findingsView report
Reviews of this site

Share your experience with inbank.ee. 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.ee.

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.