runsonwhat

TKU テレビ熊本's tech stack

What does TKU テレビ熊本 use?

TKU テレビ熊本 (tku.co.jp) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Amazon CloudFront for content delivery. Last checked .

Industry
Public Relations and Communications
Size
51–200 employees
Based in
Tokuo, Japan
Founded
1968
LinkedIn
Company page
Tools found
15
Categories
10
Layers
5 of 5
Last checked
Oct 2026

TKU テレビ熊本'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

5 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Email Delivery

TKU テレビ熊本 tech stack FAQ

What tools does TKU テレビ熊本 use?

We've found 15 tools at TKU テレビ熊本 (tku.co.jp). Edge & Hosting: Amazon CloudFront. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: Meta Pixel, WordPress and Index Exchange. Company Ops: Microsoft 365, Amazon SES and Symantec Email Security.cloud. Last checked October 3, 2026.

What email provider does TKU テレビ熊本 use?

TKU テレビ熊本 uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does TKU テレビ熊本 use?

TKU テレビ熊本 uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does TKU テレビ熊本 use?

TKU テレビ熊本 uses WordPress for its website. We found WordPress through website code.

Does TKU テレビ熊本 use Microsoft 365?

Yes. We found Microsoft 365 at TKU テレビ熊本 through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what TKU テレビ熊本 uses?

We read public traces only: TKU テレビ熊本'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.