Dragsbaek's tech stack
What does Dragsbaek use?
Dragsbaek (dragsbaek.dk) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cookiebot for security. Last checked .
- Industry
- Food Production
- Size
- 201–1,000 employees
- Based in
- Thisted, Denmark
- Founded
- 1923
- Company page
- Tools found
- 11
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Dragsbaek'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
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Dragsbaek tech stack FAQ
What tools does Dragsbaek use?
We've found 11 tools at Dragsbaek (dragsbaek.dk). Application: jQuery and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, WordPress and LinkedIn Insight Tag. Company Ops: Microsoft 365 and Cookiebot. Last checked October 4, 2026.
What email provider does Dragsbaek use?
Dragsbaek uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and DNS verification records.
What analytics tools does Dragsbaek use?
Dragsbaek uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Dragsbaek use?
Dragsbaek uses WordPress and Rank Math for its website. We found WordPress through website code.
Does Dragsbaek use Microsoft 365?
Yes. We found Microsoft 365 at Dragsbaek through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Dragsbaek uses?
We read public traces only: Dragsbaek'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.