HEMFA's tech stack
What does HEMFA use?
HEMFA (hemfa.com) uses at least 12 tools we can see from public records, including Hostinger for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Financial Services
- Size
- 11–50 employees
- Based in
- Tripoli, Libya
- Founded
- 2012
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
HEMFA'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.
Edge & Hosting
1 tool, where the bytes are served from
Hosting & Cloud
Application
6 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
HEMFA tech stack FAQ
What tools does HEMFA use?
We've found 12 tools at HEMFA (hemfa.com). Edge & Hosting: Hostinger. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365 and Resend. Last checked October 6, 2026.
What cloud does HEMFA run on?
HEMFA uses Hostinger for hosting. We found Hostinger through custom domain.
What email provider does HEMFA use?
HEMFA uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does HEMFA use?
HEMFA uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does HEMFA use?
HEMFA uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does HEMFA use Microsoft 365?
Yes. We found Microsoft 365 at HEMFA through email records. Microsoft 365 is used by 685,261 companies we track.
How does runsonwhat know what HEMFA uses?
We read public traces only: HEMFA'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.