다이닝코드's tech stack
What does 다이닝코드 use?
다이닝코드 (diningcode.com) uses at least 20 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and reCAPTCHA for security. Last checked .
- Based in
- South Korea
- Tools found
- 20
- 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
2 tools, where the bytes are served from
Hosting & Cloud
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
13 tools, how they find and keep customers
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 20 tools at 다이닝코드 (diningcode.com). Edge & Hosting: Amazon Web Services and Amazon Route 53. Application: React. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, Google Ad Manager and Microsoft Xandr. Company Ops: Google Workspace and reCAPTCHA. Last checked October 3, 2026.
What cloud does 다이닝코드 run on?
다이닝코드 uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does 다이닝코드 use?
다이닝코드 uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
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 386,987 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.