runsonwhat

Git Sicherheit's tech stack

What does Git Sicherheit use?

Git Sicherheit (git-sicherheit.de) uses at least 7 tools we can see from public records, including Microsoft 365 for email and documents, Matomo for analytics, Mailjet for email delivery and Proofpoint for security. Last checked .

Industry
Publishing
Size
1,001–5,000 employees
Based in
Weinheim, Germany
LinkedIn
Company page
Tools found
7
Categories
5
Layers
3 of 5
Last checked
Oct 2026

Git Sicherheit'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

Data & Observability

2 tools, what they measure and store

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Git Sicherheit tech stack FAQ

What tools does Git Sicherheit use?

As of October 2026, runsonwhat has found 7 tools at Git Sicherheit (git-sicherheit.de) in public records. Application: jQuery. Data & Observability: Matomo and Plausible. Company Ops: Microsoft 365, Proofpoint and Valimail. Last checked October 7, 2026.

What email provider does Git Sicherheit use?

Git Sicherheit uses Microsoft 365 for email and office software, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365. Microsoft 365 is used by 700,597 companies runsonwhat tracks.

What analytics tools does Git Sicherheit use?

Git Sicherheit uses Matomo for analytics, alongside Plausible, according to runsonwhat (October 2026). runsonwhat found Matomo through Matomo code on git-sicherheit.de. Matomo is used by 32,990 companies runsonwhat tracks.

Does Git Sicherheit use jQuery?

Yes. runsonwhat found jQuery at Git Sicherheit through jQuery code on git-sicherheit.de. jQuery is a Frontend tool used by 895,809 companies runsonwhat tracks.

How does runsonwhat know what Git Sicherheit uses?

runsonwhat reads public records only. Of the 7 tools at Git Sicherheit, 3 were found through code on git-sicherheit.de, 3 through email records and 1 through DNS records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and git-sicherheit.de about 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.