Nippon Signal's tech stack
What does Nippon Signal use?
Nippon Signal (signal.co.jp) uses at least 8 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and GlobalSign for security. Last checked .
- Based in
- Japan
- Founded
- 1928
- Tools found
- 8
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Nippon Signal'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
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Workspace
Security & Compliance
Nippon Signal tech stack FAQ
What tools does Nippon Signal use?
We've found 8 tools at Nippon Signal (signal.co.jp). Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and WordPress. Company Ops: Microsoft 365, GlobalSign and Proofpoint. Last checked October 3, 2026.
What email provider does Nippon Signal use?
Nippon Signal uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Nippon Signal use?
Nippon Signal uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Nippon Signal use?
Nippon Signal uses WordPress for its website. We found WordPress through website code.
Does Nippon Signal use Microsoft 365?
Yes. We found Microsoft 365 at Nippon Signal through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Nippon Signal uses?
We read public traces only: Nippon Signal'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.