Website report · 30 Oct 2026
www.toeken.wtf
“toeken”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).
Calls its own backend
none seen
Wallet code
none seen
Contract calls in its code
none seen
Talks to AI services
none seen
Live connections
none seen
What loads is a page only: no own backend calls, wallet code, contract calls, AI services or live connections.E10
What it is
- The Internet Archive has never saved this site, so it is probably new.E11
- The site describes itself as: “toeken holder for a living”E2
- It's built with Next.js and React (common tools for building web apps).E4E5
- Notable building blocks in its code: Three.js (3D graphics).E6
- In your browser it runs compiled WebAssembly code in your browser.E7
Where your data goes
On a first visit the page only talked to its own servers (www.toeken.wtf).
How key features work
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
E1
Page title: toeken
page title · https://www.toeken.wtf/
E2
Page description: toeken holder for a living
page description · https://www.toeken.wtf/
E3
24 request(s) to www.toeken.wtf
types: 21 script, 2 document, 1 stylesheet
GET https://www.toeken.wtf/ · script · 24 requests · network recording
E4
Next.js detected by The code reader (next-runtime)
confidence: high
www.toeken.wtf/ · “next-runtime” · The code reader analyze-web-bundle 6.4.0
E5
React detected by The code reader (react-runtime)
confidence: medium
www.toeken.wtf/_next/static/immutable/chunks/2bmkjsp3ssiol.js · “react-runtime” · The code reader analyze-web-bundle 6.4.0
E6
Three.js (3D graphics) found in the code
www.toeken.wtf/vendor/three/build/three.module.js @ 15838:18 · “THREE.WebGLRenderer” · pattern scan
E7
Uses the browser ability: webassembly
runs compiled WebAssembly code in your browser
www.toeken.wtf/vendor/meshoptimizer/meshopt_decoder.module.js @ 23:3 · “WebAssembly.instantiate(” · pattern scan
E8
Uses the browser ability: web_worker
runs work in a background thread
www.toeken.wtf/vendor/meshoptimizer/meshopt_decoder.module.js @ 78:12 · “new Worker(” · pattern scan
E9
Uses the browser ability: canvas
draws graphics on a canvas
www.toeken.wtf/vendor/three/build/three.module.js @ 1735:28 · “getContext( '2d'” · pattern scan
E10
24 requests on load: no own backend calls, wallet code, contract calls, AI services or live connections
GET https://www.toeken.wtf/ · summary · 24 requests · network recording
E11
The Internet Archive has no saved copy of toeken.wtf
page web archive · https://web.archive.org/web/*/toeken.wtf
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- The code reader hit its size budget on parts of 5 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id FFe3b9W4.