Ordine degli Avvocati di Taranto's tech stack
What does Ordine degli Avvocati di Taranto use?
Ordine degli Avvocati di Taranto (oravta.it) uses at least 8 tools we can see from public records, including WordPress for its website, Brevo for marketing, Cloudflare for content delivery and Elastic Email for email delivery. Last checked .
- Industry
- Legal Services
- Size
- 1,001–5,000 employees
- Based in
- Taranto, Italy
- Company page
- Tools found
- 8
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Ordine degli Avvocati di Taranto'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
3 tools, what the product is built with
Frontend
Media & UI
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Email Delivery
Ordine degli Avvocati di Taranto tech stack FAQ
What tools does Ordine degli Avvocati di Taranto use?
We've found 8 tools at Ordine degli Avvocati di Taranto (oravta.it). Edge & Hosting: Cloudflare. Application: jQuery, Font Awesome and YouTube. Go-to-market: WordPress and Brevo. Company Ops: Elastic Email. Last checked October 3, 2026.
What CMS does Ordine degli Avvocati di Taranto use?
Ordine degli Avvocati di Taranto uses WordPress for its website. We found WordPress through website code.
What marketing software does Ordine degli Avvocati di Taranto use?
Ordine degli Avvocati di Taranto uses Brevo for marketing. We found Brevo through DNS verification records.
Does Ordine degli Avvocati di Taranto use Cloudflare?
Yes. We found Cloudflare at Ordine degli Avvocati di Taranto through DNS records and website code. Cloudflare is used by 311,291 companies we track.
How does runsonwhat know what Ordine degli Avvocati di Taranto uses?
We read public traces only: Ordine degli Avvocati di Taranto'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.