runsonwhat

Page not found's tech stack

What does Page not found use?

Page not found (koza.rocks) uses at least 6 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents and SendGrid for email delivery. Last checked .

Tools found
6
Categories
6
Layers
3 of 5
Last checked
Nov 2026

Page not found's stack, layer by layer

Of 6 tools, 4 came from website code and 2 from email records. 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

3 tools, what the product is built with

Frontend

Backend & Database

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Page not found tech stack FAQ

What tools does Page not found use?

As of November 2026, runsonwhat has found 6 tools at Page not found (koza.rocks) in public records. Edge & Hosting: Google Cloud. Application: Google Fonts, Firebase and Nuxt. Company Ops: Google Workspace and SendGrid. Last checked November 6, 2026.

What cloud does Page not found run on?

Page not found uses Google Cloud for hosting and cloud infrastructure, according to runsonwhat (November 2026). runsonwhat found Google Cloud through Google Cloud code on koza.rocks. Google Cloud is used by 77,800 companies runsonwhat tracks.

What email provider does Page not found use?

Page not found uses Google Workspace for email and office software, according to runsonwhat (November 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 420,115 companies runsonwhat tracks.

Does Page not found use Google Fonts?

Yes. runsonwhat found Google Fonts at Page not found through Google Fonts code on koza.rocks. Google Fonts is a Media & UI tool used by 825,558 companies runsonwhat tracks.

How does runsonwhat know what Page not found uses?

runsonwhat reads public records only. Of the 6 tools at Page not found, 4 were found through code on koza.rocks, 2 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and koza.rocks about 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.