ZIEGLER Firefighting Vehicles's tech stack
What does ZIEGLER Firefighting Vehicles use?
ZIEGLER Firefighting Vehicles (ziegler.de) uses at least 6 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Amazon SES for email delivery and Cookiebot for security. Last checked .
- Based in
- Germany
- Founded
- 1891
- Company page
- Tools found
- 6
- Categories
- 5
- Layers
- 3 of 5
- Last checked
- Oct 2026
ZIEGLER Firefighting Vehicles'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.
Application
1 tool, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
ZIEGLER Firefighting Vehicles tech stack FAQ
What tools does ZIEGLER Firefighting Vehicles use?
We've found 6 tools at ZIEGLER Firefighting Vehicles (ziegler.de). Application: Font Awesome. Data & Observability: Google Analytics. Company Ops: Microsoft 365, Google Workspace and Amazon SES. Last checked October 2, 2026.
What email provider does ZIEGLER Firefighting Vehicles use?
ZIEGLER Firefighting Vehicles uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does ZIEGLER Firefighting Vehicles use?
ZIEGLER Firefighting Vehicles uses Google Analytics for analytics. We found Google Analytics through website code.
Does ZIEGLER Firefighting Vehicles use Microsoft 365?
Yes. We found Microsoft 365 at ZIEGLER Firefighting Vehicles through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what ZIEGLER Firefighting Vehicles uses?
We read public traces only: ZIEGLER Firefighting Vehicles'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.