Website report · 30 Oct 2026

t.me

“Telegram: View @cyberleekario”

AI-written from evidence · anthropic 11 evidence items Code reader analysed 4 scripts
What this means for you

This is Telegram's public preview page for the account @cyberleekario, which describes itself as 'Fighting For The Gamer's Rights.'E1E2E3

  • You are looking at a page run by Telegram, not by the account owner. It shows a short preview of the @cyberleekario profile.E1E3
  • Loading this page sets one cookie from t.me, kept for about a day. No cookies from other companies were set.E8
  • We saw no trackers, wallet code, contract calls or AI services when this page loaded.E10
  • The profile description links to cyberleek.arwe.io. That is a separate site, and this check does not cover it.E2

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 page sits on t.me, Telegram's short web address. The Internet Archive has saved t.me since 2010.E4E11
  • It shows the account's name and description: 'Fighting For The Gamer's Rights,' plus a web link.E1E2
  • The page is simple. It made 10 requests in total and called no backend (behind-the-scenes server) of its own.E10
  • The page includes a tg://resolve link, a link that opens the Telegram app, so you can view the account there.E7

Where your data goes

Social & embedsEmbedded videos, posts and share buttons. 1
telegram.orgTelegram: Telegram widget 7×E5
Not identifiedServices we don't have in our list yet. 2
cdn4.telesco.penot identified 1×E6
resolvenot identified 1×E7

Cookies and storage

Names only. We never store the values.

CookieSet forKeptWhose
stel_ssidE8t.me about 1 daysthe site

Pages and API calls

Pages it links to

/s

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: Telegram: View @cyberleekario
page title · https://t.me/cyberleekario
E2
Page description: Fighting For The Gamer’s Rights. https://cyberleek.arwe.io
page description · https://t.me/cyberleekario
E3
Site name: Telegram
page site_name · https://t.me/cyberleekario
E4
1 request(s) to t.me
types: 1 document
GET https://t.me/cyberleekario · document · network recording
E5
7 request(s) to telegram.org
types: 3 stylesheet, 2 font, 1 script
GET https://telegram.org/css/font-roboto.css · stylesheet · 7 requests · network recording
E6
1 request(s) to cdn4.telesco.pe
types: 1 image
GET https://cdn4.telesco.pe/file/g7o8vi8qkoEv5lcnZoRmve8wF0OSHNlWXbfUk4S_qPyLy6JukjLon5cqHlgpLoXVm2Y52C8mEZPCFyEcK5v… · image · network recording
E7
1 request(s) to resolve
types: 1 document
GET tg://resolve · document · network recording
E8
Cookie 'stel_ssid' set for t.me
kept for about 1 days
cookie stel_ssid on t.me · value not stored
E9
1 links to pages on the same site
page links · https://t.me/cyberleekario · /s
E10
10 requests on load: no own backend calls, wallet code, contract calls, AI services or live connections
GET https://t.me/cyberleekario · summary · 10 requests · network recording
E11
The Internet Archive first saved t.me on 2010-11-27 and has snapshots from 2000 different days
page web archive · https://web.archive.org/web/20101127071701/t.me

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).
  • We only saw what your browser loads when you open this page. Anything Telegram does on its own servers is invisible to us.
  • We did not check the linked site cyberleek.arwe.io or the account's posts inside the Telegram app.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id EkOtI4F7.