Skip to main content

Security report for bankofgeorgia.ge

საქართველოს ბანკი · Finance · Georgia

Partial score · DNS & email only

66/100

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

The Bank of Georgia's official retail website serves as a primary digital channel for retail banking customers in Georgia. The site presents a professional and consistent brand image with a focus on retail banking services such as loans, deposits, and cards. The domain age and WHOIS data confirm the bank's long-standing presence and legitimacy in the Georgian financial sector. Technically, the website employs modern web technologies including JavaScript frameworks, Google Tag Manager, Google Analytics, PostHog analytics, and Google reCAPTCHA for bot protection. The use of service workers indicates a progressive web app approach enhancing user experience. Security posture is strong with HTTPS enforced and bot protection mechanisms; however, explicit security headers and published security policies are absent, representing an area for improvement. Privacy compliance is limited as no explicit privacy or cookie policies were found in the analyzed content, and no consent mechanisms are evident. Contact information such as emails or phone numbers is not present in the provided HTML, which may impact user trust and support accessibility. Overall, the website is well-designed, performant, and trustworthy but would benefit from enhanced transparency in privacy and security policies.

Scanned

This is an earlier scan of bankofgeorgia.ge. View the latest report

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
6of 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

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

    • 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

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics

      What to do: Document all third-party data sharing in your privacy policy

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching bankofgeorgia.ge

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
72
Email security
60
DNS health
65
Network security
100
GDPR outside view
35
Average
66

Not counted

  • Security headers: did not complete in this scan.
  • 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

Bank of Georgia holds a leading position in the Georgian retail banking market, targeting local consumers with a comprehensive suite of banking products. The business model focuses on retail financial services, leveraging digital channels for customer engagement. The website reflects a mature digital presence with integration of analytics and marketing tools, indicating ongoing investment in digital transformation. The absence of visible contact details and policy documents suggests potential gaps in customer support and regulatory compliance communication. The bank likely operates a broader ecosystem including related domains such as account.bog.ge for account management. The long domain registration history and consistent WHOIS data reinforce the bank's credibility and market stability.

Security posture

The website demonstrates a solid security foundation with HTTPS encryption and Google reCAPTCHA integration to mitigate automated abuse. The registration of a service worker suggests attention to modern web security and performance practices. However, the lack of explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces defense-in-depth. No visible vulnerabilities or exposed sensitive data were detected in the HTML content. The absence of published security policies or incident response contacts limits transparency and may hinder effective incident management. Privacy compliance is minimal, with no GDPR-specific disclosures or cookie consent mechanisms evident. Overall, the security posture is good but could be enhanced by formalizing security policies and improving header configurations.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with clear GDPR compliance statements and consent mechanisms.
  2. Add explicit security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen browser security.
  3. Provide clear contact information including security incident response and data protection officer contacts to improve transparency and user trust.
  4. Enhance accessibility features to meet higher standards and improve user experience for all visitors.
  5. Regularly audit third-party scripts and analytics tools to ensure no vulnerable libraries are included and maintain minimal user tracking consistent with privacy commitments.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
საქართველოს ბანკი
Description
საქართველოს ბანკის ოფიციალური ვებ-გვერდი. ცხოვრება არის ზმნა. იმოქმედე, არ გაჩერდე!
Key services
Retail banking, Loans, Deposits, Cards
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Google Analytics, Google reCAPTCHA, PostHog analytics, Service Worker, Web Components
Frameworks
Bog Design System
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for bot protection
  • Service Worker registered
  • Content Security Policy not explicitly found in HTML
  • No visible exposed sensitive data

Analytics and tracking

Services
Google Analytics, PostHog
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
PostHog
Marketing tools
PostHog
Transparency
basic

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 challenges
  2. Content is primarily in Georgian language targeting local retail banking customers
  3. No explicit privacy, cookie, or terms of service policies found in the provided HTML
  4. No contact emails or phone numbers explicitly found in the HTML content
  5. Strong use of modern web technologies and analytics tools
  6. Security best practices partially implemented but missing explicit security headers
  7. WHOIS data supports legitimacy and long-term operation
Technical notes

Notes

The website uses a modern JavaScript-based tech stack with custom design system components (Bog Design System) and progressive web app features such as service workers. Analytics and marketing integrations include Google Tag Manager, Google Analytics, and PostHog, indicating a mature data-driven approach. The site is mobile optimized with responsive design and preloaded fonts for performance. No CMS or hosting provider details were explicitly found. Performance is moderate with asynchronous script loading and preconnect hints to external domains. The absence of explicit CMS or hosting info suggests a custom or proprietary platform. Technical debt appears low, but improvements in accessibility and security header implementation are recommended to reduce risk and improve compliance.
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. 65/100Medium33 findingsView report
Reviews of this site

Share your experience with bankofgeorgia.ge. 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 bankofgeorgia.ge.

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.