Tamar Petroleum Ltd's tech stack
What does Tamar Petroleum Ltd use?
Tamar Petroleum Ltd (tamarpetroleum.co.il) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Based in
- Israel
- Founded
- 2017
- Tools found
- 9
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Tamar Petroleum Ltd'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
CDN & Edge
Application
5 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Website & CMS
Company Ops
1 tool, what the team runs on day to day
Workspace
Tamar Petroleum Ltd tech stack FAQ
What tools does Tamar Petroleum Ltd use?
We've found 9 tools at Tamar Petroleum Ltd (tamarpetroleum.co.il). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Microsoft 365. Last checked October 4, 2026.
What email provider does Tamar Petroleum Ltd use?
Tamar Petroleum Ltd uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Tamar Petroleum Ltd use?
Tamar Petroleum Ltd uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Tamar Petroleum Ltd use?
Tamar Petroleum Ltd uses WordPress for its website. We found WordPress through website code.
Does Tamar Petroleum Ltd use Microsoft 365?
Yes. We found Microsoft 365 at Tamar Petroleum Ltd through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Tamar Petroleum Ltd uses?
We read public traces only: Tamar Petroleum Ltd'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.