Landesfischereiverband Südtirol's tech stack
What does Landesfischereiverband Südtirol use?
Landesfischereiverband Südtirol (fischereiverband.it) uses at least 11 tools we can see from public records, including Aruba.it for hosting, WordPress for its website, Taggbox for marketing and Cookiebot for security. Last checked .
- Based in
- Italy
- Tools found
- 11
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Landesfischereiverband Südtirol'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
5 tools, what the product is built with
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Landesfischereiverband Südtirol tech stack FAQ
What tools does Landesfischereiverband Südtirol use?
We've found 11 tools at Landesfischereiverband Südtirol (fischereiverband.it). Edge & Hosting: Aruba.it. Application: jQuery, Google Fonts and Font Awesome. Go-to-market: WordPress, WooCommerce and Taggbox. Company Ops: Cookiebot. Last checked October 4, 2026.
What cloud does Landesfischereiverband Südtirol run on?
Landesfischereiverband Südtirol uses Aruba.it for hosting. We found Aruba.it through email records.
What CMS does Landesfischereiverband Südtirol use?
Landesfischereiverband Südtirol uses WordPress and WooCommerce for its website. We found WordPress through website code.
What marketing software does Landesfischereiverband Südtirol use?
Landesfischereiverband Südtirol uses Taggbox for marketing. We found Taggbox through website code.
Does Landesfischereiverband Südtirol use jQuery?
Yes. We found jQuery at Landesfischereiverband Südtirol through website code. jQuery is used by 67,244 companies we track.
How does runsonwhat know what Landesfischereiverband Südtirol uses?
We read public traces only: Landesfischereiverband Südtirol'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.