runsonwhat

Bank Eskhata's tech stack

What does Bank Eskhata use?

Bank Eskhata (eskhata.com) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, LinkedIn for marketing and reCAPTCHA for security. Last checked .

Industry
Financial Services
Size
1,001–5,000 employees
Based in
Khŭjand, Tajikistan
Founded
1994
LinkedIn
Company page
Tools found
12
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Bank Eskhata's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Application

4 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Bank Eskhata tech stack FAQ

What tools does Bank Eskhata use?

We've found 12 tools at Bank Eskhata (eskhata.com). Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and LinkedIn. Company Ops: Microsoft 365 and reCAPTCHA. Last checked October 2, 2026.

What email provider does Bank Eskhata use?

Bank Eskhata uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Bank Eskhata use?

Bank Eskhata uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What marketing software does Bank Eskhata use?

Bank Eskhata uses LinkedIn for marketing. We found LinkedIn through DNS verification records.

Does Bank Eskhata use Microsoft 365?

Yes. We found Microsoft 365 at Bank Eskhata through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Bank Eskhata uses?

We read public traces only: Bank Eskhata's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.