Fuji Morinaga Milk Industry's tech stack
What does Fuji Morinaga Milk Industry use?
Fuji Morinaga Milk Industry (fujinyugyo.jp) uses at least 9 tools we can see from public records, including Google Tag Manager for analytics, WordPress for its website, Amazon CloudFront for content delivery and GlobalSign for security. Last checked .
- Based in
- Japan
- Founded
- 1966
- Tools found
- 9
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Fuji Morinaga Milk Industry'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
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Fuji Morinaga Milk Industry tech stack FAQ
What tools does Fuji Morinaga Milk Industry use?
We've found 9 tools at Fuji Morinaga Milk Industry (fujinyugyo.jp). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery and Google Fonts. Data & Observability: Google Tag Manager. Go-to-market: WordPress and All in One SEO. Company Ops: GlobalSign. Last checked October 4, 2026.
What analytics tools does Fuji Morinaga Milk Industry use?
Fuji Morinaga Milk Industry uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
What CMS does Fuji Morinaga Milk Industry use?
Fuji Morinaga Milk Industry uses WordPress and All in One SEO for its website. We found WordPress through website code.
Does Fuji Morinaga Milk Industry use jQuery?
Yes. We found jQuery at Fuji Morinaga Milk Industry through website code. jQuery is used by 67,244 companies we track.
How does runsonwhat know what Fuji Morinaga Milk Industry uses?
We read public traces only: Fuji Morinaga Milk Industry'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.