Senken Shinbunsha's tech stack
What does Senken Shinbunsha use?
Senken Shinbunsha (senken.co.jp) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Amazon CloudFront for content delivery and SendGrid for email delivery. Last checked .
- Industry
- Journalism
- Size
- 1–10 employees
- Based in
- Tokyo, Japan
- Founded
- 1956
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Senken Shinbunsha'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
Data & Observability
3 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Senken Shinbunsha tech stack FAQ
What tools does Senken Shinbunsha use?
We've found 12 tools at Senken Shinbunsha (senken.co.jp). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Microsoft 365 and SendGrid. Last checked October 3, 2026.
What email provider does Senken Shinbunsha use?
Senken Shinbunsha uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Senken Shinbunsha use?
Senken Shinbunsha uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does Senken Shinbunsha use Microsoft 365?
Yes. We found Microsoft 365 at Senken Shinbunsha through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Senken Shinbunsha uses?
We read public traces only: Senken Shinbunsha'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.