trenchcoat
Free · no sign-up
Website report · 20 h ago

www.duge.wtf

“duge”

Template-written 14 evidence items Code reader analysed 17 scripts
What this means for you

www.duge.wtf talked to 2 outside services on a first visit.E5E4

  • What loads is a page only: no calls to its own backend, no wallet code, no contract calls, no AI services and no live connections.E13
  • We saw no known analytics or advertising services load on the first visit.E1
  • Its code still includes Vercel Analytics, which may switch on later (for example after you accept cookies or sign in).E10

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.E13

What it is

  • The Internet Archive first saved this site on 2026-11-07 (0 days ago).E14
  • The site describes itself as: “Just Duge”E2
  • It's built with React and Next.js (common tools for building web apps).E7E8
  • Notable building blocks in its code: Three.js (3D graphics).E9
  • In your browser it saves small bits of data in your browser.E11

Where your data goes

FontsDownload typefaces. 2
fonts.gstatic.comGoogle Fonts: fonts 2×E5
fonts.googleapis.comGoogle Fonts: fonts 1×E4

How key features work

Drawing and editing in the browser

The page draws and edits graphics in your browser using Three.js (3D graphics) and the canvas.E9E12

Three.js (3D graphics)canvas

Measuring what you do

Visits and clicks are measured with Vercel Analytics (found in its traffic or its code).E10

Vercel Analytics

Saving data on your device

It saves data in your browser (localStorage), so some things persist between visits.E11E6

local_storagelocalStorage

Cookies and storage

Names only. We never store the values.

localStorageE6: cm-look-v2

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: duge
page title · https://www.duge.wtf/
E2
Page description: Just Duge
page description · https://www.duge.wtf/
E3
33 request(s) to www.duge.wtf
types: 19 image, 10 script, 2 document
GET https://www.duge.wtf/ · image · 33 requests · network recording
E4
1 request(s) to fonts.googleapis.com
types: 1 stylesheet
GET https://fonts.googleapis.com/css2 · stylesheet · network recording
E5
2 request(s) to fonts.gstatic.com
types: 2 font
GET https://fonts.gstatic.com/s/bowlbyone/v25/taiPGmVuC4y96PFeqp8sqomI_A.woff2 · font · 2 requests · network recording
E6
localStorage: 1 key(s) saved in your browser
localStorage keys: cm-look-v2 · values not stored
E7
React detected by the code reader (react-runtime)
confidence: medium
www.duge.wtf/_next/static/immutable/chunks/3ov2b25xs-z64.js · “react-runtime” · the code reader
E8
Next.js detected by the code reader (next-runtime)
confidence: high
www.duge.wtf/ · “next-runtime” · the code reader
E9
Three.js (3D graphics) found in the code
www.duge.wtf/vendor/three/three.min.js @ 6:247790 · “THREE.WebGLRenderer” · pattern scan
E10
Vercel Analytics found in the code
www.duge.wtf/ (page HTML) @ 1:1192 · “/_vercel/insights” · pattern scan
E11
Uses the browser ability: local_storage
saves small bits of data in your browser
www.duge.wtf/_vercel/insights/script.js @ 1:891 · “localStorage.setItem(” · pattern scan
E12
Uses the browser ability: canvas
draws graphics on a canvas
www.duge.wtf/vendor/three/three.min.js @ 6:10643 · “getContext("2d"” · pattern scan
E13
36 requests on load: no own backend calls, wallet code, contract calls, AI services or live connections
GET https://www.duge.wtf/ · summary · 36 requests · network recording
E14
The Internet Archive first saved duge.wtf on 2026-11-07 and has snapshots from 1 different days
page web archive · https://web.archive.org/web/20261107112417/duge.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 tpzXF9ap.