Yamaguchi Aburaya Fukutaro's tech stack
What does Yamaguchi Aburaya Fukutaro use?
Yamaguchi Aburaya Fukutaro (fukutaro.co.jp) uses at least 8 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Based in
- Japan
- Founded
- 1955
- Tools found
- 8
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Yamaguchi Aburaya Fukutaro'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
3 tools, how they find and keep customers
Company Ops
1 tool, what the team runs on day to day
Workspace
Yamaguchi Aburaya Fukutaro tech stack FAQ
What tools does Yamaguchi Aburaya Fukutaro use?
We've found 8 tools at Yamaguchi Aburaya Fukutaro (fukutaro.co.jp). Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Microsoft Clarity. Go-to-market: Meta Pixel and WordPress. Company Ops: Microsoft 365. Last checked October 3, 2026.
What email provider does Yamaguchi Aburaya Fukutaro use?
Yamaguchi Aburaya Fukutaro uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does Yamaguchi Aburaya Fukutaro use?
Yamaguchi Aburaya Fukutaro uses Google Analytics and Microsoft Clarity for analytics. We found Google Analytics through website code.
What CMS does Yamaguchi Aburaya Fukutaro use?
Yamaguchi Aburaya Fukutaro uses WordPress for its website. We found WordPress through website code.
Does Yamaguchi Aburaya Fukutaro use Microsoft 365?
Yes. We found Microsoft 365 at Yamaguchi Aburaya Fukutaro through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Yamaguchi Aburaya Fukutaro uses?
We read public traces only: Yamaguchi Aburaya Fukutaro'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.