Website report · 39 min ago
hype.gg
“Checking your browser…”
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.E8
What it is
Where your data goes
Pages and API calls
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: Checking your browser…
page title · https://hype.gg/
E2
Main heading: Checking your browser
page h1 · https://hype.gg/
E3
1 request(s) to hype.gg
types: 1 document
GET https://hype.gg/ · document · network recording
E4
8 request(s) to challenges.cloudflare.com
types: 2 script, 2 xhr, 2 image
GET https://challenges.cloudflare.com/turnstile/v0/api.js · script · 8 requests · network recording
E5
1 request(s) to brunhild.challenges.cloudflare.com
types: 1 fetch
GET https://brunhild.challenges.cloudflare.com/cdn-cgi/challenge-platform/h/b/i/a5aa1728dc17cf49/ChSXYib2TojHQnbp4SyB1RfACYGd6zfnWVB0H-… · fetch · network recording
E6
Cloudflare Turnstile found in the code
hype.gg/ (page HTML) @ 5:26 · “challenges.cloudflare.com/turnstile” · pattern scan
E7
Code reader found the endpoint /.railway/__challenge
how: call:fetch
hype.gg/ @ 12:8 · “/.railway/__challenge” · the code reader
E8
10 requests on load: no own backend calls, wallet code, contract calls, AI services or live connections
GET https://hype.gg/ · summary · 10 requests · network recording
E9
The Internet Archive first saved hype.gg on 2017-04-20 and has snapshots from 29 different days
page web archive · https://web.archive.org/web/20170420074419/hype.gg
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.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id W9mP9BrU.