runsonwhat

クレジットカードはライフカード's tech stack

What does クレジットカードはライフカード use?

クレジットカードはライフカード (lifecard.co.jp) uses at least 15 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 .

Based in
Japan
Founded
1948
Tools found
15
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

6 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Security & Compliance

クレジットカードはライフカード tech stack FAQ

What tools does クレジットカードはライフカード use?

We've found 15 tools at クレジットカードはライフカード (lifecard.co.jp). Edge & Hosting: Amazon CloudFront. Application: Google Fonts. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Microsoft 365, SendGrid and Imperva. Last checked October 3, 2026.

What email provider does クレジットカードはライフカード use?

クレジットカードはライフカード uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification 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. Microsoft 365 is used by 269,769 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.