Lillywhites's tech stack
What does Lillywhites use?
Lillywhites (lillywhites.com) uses at least 6 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Zendesk for customer support and Cloudflare for content delivery. Last checked .
- Industry
- Sporting Goods
- Size
- 51–200 employees
- Based in
- Shirebrook, United Kingdom
- Founded
- 1925
- Company page
- Tools found
- 6
- Categories
- 6
- Layers
- 3 of 5
- Last checked
- Oct 2026
Lillywhites'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
2 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Lillywhites tech stack FAQ
What tools does Lillywhites use?
We've found 6 tools at Lillywhites (lillywhites.com). Edge & Hosting: Cloudflare and Microsoft Azure. Go-to-market: Zendesk. Company Ops: Microsoft 365 and GlobalSign. Last checked October 3, 2026.
What cloud does Lillywhites run on?
Lillywhites uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain.
What email provider does Lillywhites use?
Lillywhites uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What does Lillywhites use for customer support?
Lillywhites uses Zendesk for customer support. We found Zendesk through custom domain and email records.
Does Lillywhites use Microsoft 365?
Yes. We found Microsoft 365 at Lillywhites through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Lillywhites uses?
We read public traces only: Lillywhites'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.