runsonwhat

東急・東急電鉄公式サイト's tech stack

What does 東急・東急電鉄公式サイト use?

東急・東急電鉄公式サイト (tokyu.co.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 PowerDMARC for security. Last checked .

Industry
Public Transport
Based in
Japan
Founded
1922
Tools found
11
Categories
8
Layers
5 of 5
Last checked
Oct 2026

東急・東急電鉄公式サイト'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

1 tool, where the bytes are served from

Application

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Dev Tools

Security & Compliance

東急・東急電鉄公式サイト tech stack FAQ

What tools does 東急・東急電鉄公式サイト use?

We've found 11 tools at 東急・東急電鉄公式サイト (tokyu.co.jp). Edge & Hosting: Amazon CloudFront. Application: Next.js. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel and Google Ads. Company Ops: Microsoft 365, Atlassian and PowerDMARC. Last checked October 4, 2026.

What email provider does 東急・東急電鉄公式サイト use?

東急・東急電鉄公式サイト uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does 東急・東急電鉄公式サイト use?

東急・東急電鉄公式サイト uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

Does 東急・東急電鉄公式サイト use Microsoft 365?

Yes. We found Microsoft 365 at 東急・東急電鉄公式サイト through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what 東急・東急電鉄公式サイト uses?

We read public traces only: 東急・東急電鉄公式サイト'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.