Turriziani Petroli's tech stack
What does Turriziani Petroli use?
Turriziani Petroli (turrizianipetroli.it) uses at least 8 tools we can see from public records, including Aruba.it for hosting, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Oil & Gas
- Size
- 51–200 employees
- Based in
- Roma, Italy
- Founded
- 1966
- Company page
- Tools found
- 8
- Categories
- 5
- Layers
- 4 of 5
- Last checked
- Oct 2026
Turriziani Petroli'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
4 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Turriziani Petroli tech stack FAQ
What tools does Turriziani Petroli use?
We've found 8 tools at Turriziani Petroli (turrizianipetroli.it). Edge & Hosting: Aruba.it. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Last checked October 4, 2026.
What cloud does Turriziani Petroli run on?
Turriziani Petroli uses Aruba.it for hosting. We found Aruba.it through email records.
What analytics tools does Turriziani Petroli use?
Turriziani Petroli uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Turriziani Petroli use?
Turriziani Petroli uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Turriziani Petroli use Google Analytics?
Yes. We found Google Analytics at Turriziani Petroli through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Turriziani Petroli uses?
We read public traces only: Turriziani Petroli'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.