ロッテリア公式サイト|LOTTERIA's tech stack
What does ロッテリア公式サイト|LOTTERIA use?
ロッテリア公式サイト|LOTTERIA (lotteria.jp) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Amazon CloudFront for content delivery and Trend Micro for security. Last checked .
- Industry
- Wholesale
- Size
- 201–1,000 employees
- Based in
- Minato, Japan
- Founded
- 1972
- Company page
- Tools found
- 11
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
ロッテリア公式サイト|LOTTERIA'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
4 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
1 tool, how they find and keep customers
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
ロッテリア公式サイト|LOTTERIA tech stack FAQ
What tools does ロッテリア公式サイト|LOTTERIA use?
We've found 11 tools at ロッテリア公式サイト|LOTTERIA (lotteria.jp). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365 and Trend Micro. Last checked October 4, 2026.
What email provider does ロッテリア公式サイト|LOTTERIA use?
ロッテリア公式サイト|LOTTERIA uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does ロッテリア公式サイト|LOTTERIA use?
ロッテリア公式サイト|LOTTERIA uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does ロッテリア公式サイト|LOTTERIA use Microsoft 365?
Yes. We found Microsoft 365 at ロッテリア公式サイト|LOTTERIA through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what ロッテリア公式サイト|LOTTERIA uses?
We read public traces only: ロッテリア公式サイト|LOTTERIA'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.