Skip to main content

Security report for capitalbank.jo

Capital Bank of Jordan · Finance · Jordan

Low risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

78/100

Risk levelLow

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

Capital Bank of Jordan operates as a regional banking institution providing a wide range of financial services including personal, institutional, investment, and corporate banking primarily in Jordan and Iraq. The website presents a professional and consistent brand image with detailed navigation covering various banking products and services. The target audience includes personal and institutional customers seeking banking solutions in these markets. The business model focuses on traditional and digital banking services with an emphasis on innovation and customer-centric solutions. Technically, the website employs modern web technologies including Google Tag Manager, Google Analytics, Facebook Pixel, and interactive chat widgets, indicating a mature digital infrastructure. The site is mobile-optimized and uses HTTPS, contributing to a secure and user-friendly experience. However, accessibility features are basic and SEO optimization is moderate. From a security perspective, the site enforces HTTPS and uses asynchronous loading of tracking scripts, but lacks visible security headers and explicit privacy or cookie policies. There is no public incident response or vulnerability disclosure information, which could be improved to enhance trust and compliance. No WAF or blocking mechanisms were detected, and the domain registration data aligns well with the business claims, supporting legitimacy. Overall, the website scores well in business credibility and technical implementation but requires improvements in privacy compliance and security transparency to reach a higher maturity level. Strategic recommendations include publishing comprehensive privacy and cookie policies, implementing security headers, and providing clear incident response contacts.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

4 findings rated critical or high. Fix these first.

  1. 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"

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

  3. 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching capitalbank.jo

This scan found 16 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
75
Security headers
70
Email security
85
DNS health
85
Network security
100
GDPR outside view
53
Average
78

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

Capital Bank of Jordan holds a strong position in the Jordanian and Iraqi banking markets, offering a comprehensive suite of banking products tailored to personal, SME, commercial, and corporate clients. The bank leverages digital channels such as an Open Banking Portal and mobile applications to enhance customer engagement. Its competitive advantages include a broad product portfolio, regional presence, and integration of modern digital tools. Revenue streams likely derive from traditional banking fees, loans, deposits, and digital banking services. The partnership ecosystem includes technology providers for analytics and chat services. The bank's operations reflect a focus on innovation and customer service, positioning it well for growth in its target markets.

Security posture

The website demonstrates a moderate security posture with HTTPS enforced and use of reputable analytics and tracking tools loaded asynchronously. However, the absence of key security headers such as Content-Security-Policy and Strict-Transport-Security reduces protection against common web attacks. Lack of visible privacy and cookie policies, as well as missing incident response contacts, indicates gaps in compliance and transparency. No vulnerabilities or exposed sensitive data were detected in the provided content. The security score reflects these strengths and weaknesses, suggesting the bank should enhance its security policies and disclosures to align with best practices and regulatory requirements.

Recommendations

  1. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements and consent mechanisms.
  2. Implement and configure essential security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Strict-Transport-Security.
  3. Provide explicit security incident response contact information and establish a vulnerability disclosure program.
  4. Enhance accessibility features to improve compliance and user experience for all users.
  5. Regularly audit third-party scripts and tracking tools to ensure privacy compliance and minimize security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Capital Bank of Jordan
Description
Providing innovative, simplified, and holistic financial solutions through enhanced products in the Jordanian and Iraqi markets.
Key services
Personal banking programs, Accounts, Loans, Cards, Deposits, Bancassurance, Capital Rewards, Personal Transfers, Ways to bank, Open Banking Portal
Content quality
good
Branding
consistent

Technology

Stack
Google Tag Manager, Google Analytics, Facebook Pixel, ReadSpeaker, PureCloud Webchat Widget, CSS3, JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Use of Google Tag Manager and Facebook Pixel with async loading

Analytics and tracking

Services
Google Analytics, Facebook Pixel
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed with clear navigation and consistent branding
  2. No explicit privacy, cookie, or terms of service policies found in the provided content
  3. No visible contact emails or phone numbers found in the provided HTML snippet
  4. Use of modern tracking and analytics tools without visible privacy compliance mechanisms
  5. No visible security.txt or vulnerability disclosure information
  6. Multiple external domains used for analytics, chat, and fonts
  7. No signs of WAF or content blocking detected
Technical notes

Notes

The website uses a modern technology stack with asynchronous loading of analytics and tracking scripts such as Google Tag Manager, Google Analytics, and Facebook Pixel, which supports efficient performance and user tracking. The inclusion of ReadSpeaker and PureCloud Webchat widgets indicates investment in accessibility and customer support technologies. The site is mobile-optimized with responsive design elements and preloaded fonts for performance. However, no specific CMS or hosting provider information was detected. Performance is moderate, with opportunities to improve SEO and accessibility. Technical risks include reliance on multiple third-party scripts without visible privacy controls and lack of security headers, which could impact security and 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

Reviews of this site

Share your experience with capitalbank.jo. 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 capitalbank.jo.

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.