新潟縣信用組合's tech stack
What does 新潟縣信用組合 use?
新潟縣信用組合 (niigata-kenshin.co.jp) uses at least 8 tools we can see from public records, including Microsoft Azure for hosting, Apple Business for email and documents, Google Analytics for analytics and GlobalSign for security. Last checked .
- Based in
- Japan
- Founded
- 1950
- Tools found
- 8
- Categories
- 7
- 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
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Media & UI
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
新潟縣信用組合 tech stack FAQ
What tools does 新潟縣信用組合 use?
We've found 8 tools at 新潟縣信用組合 (niigata-kenshin.co.jp). Edge & Hosting: Microsoft Azure. Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Apple Business and GlobalSign. Last checked October 3, 2026.
What cloud does 新潟縣信用組合 run on?
新潟縣信用組合 uses Microsoft Azure for hosting. We found Microsoft Azure through DNS records.
What email provider does 新潟縣信用組合 use?
新潟縣信用組合 uses Apple Business for email and documents. We found Apple Business through DNS verification records.
What analytics tools does 新潟縣信用組合 use?
新潟縣信用組合 uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does 新潟縣信用組合 use Google Analytics?
Yes. We found Google Analytics at 新潟縣信用組合 through website code. Google Analytics is used by 89,943 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.