Channel
@Web_Security_Channel
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,028subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001280512806 |
|---|---|
| Type | Channel |
| Username | @Web_Security_Channel |
| Created | Between 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Web_Security_Channel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 11:54 | 1,028 | -1 |
| 9 Aug 2026, 17:41 | 1,029 | -2 |
| 7 Aug 2026, 02:49 | 1,031 | no change |
| 6 Aug 2026, 20:03 | 1,031 | first reading |
20 posts held, back to 12 May 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 April 2024. An engagement rate over an empty window would be a number about nothing.
📱 Новая версия трояна Vultur под маской McAfee Security угрожает пользователям Android Новый отчет по кибербезопасности выявил усовершенствованную версию банковского трояна Vultur для Android, сложнее обнаруживаемую антивирусами из-за продвинутых функций удаленного доступа и методов маскировки. Впервые замеченный в 2022 году, Vultur умеет захватывать экраны и записывать нажатия клавиш, угрожая банковским данным. За …
🔓 Взломанные сайты WordPress используют для брутфорса паролей других ресурсов Сайты на WordPress снова оказались в центре масштабной хакерской кампании. Однако исследователи Sucuri предупреждают об изменении целей злоумышленников. Взломанные сайты используются для брутфорса паролей других веб-ресурсов через браузеры посетителей. Исследователи считают, что взлом сайтов в этом случае выступает не как самоцель. Вероят…
❕ Печатает 👨💻 Создание анонимного канала связи с помощью IRC и Tor ЧИТАТЬ Channel | Chat | Live
1️⃣2️⃣3️⃣4️⃣5️⃣ Бесплатно только для подписчиков проекта Web Security! Встречайте нашего нового помощника — бота на базе нейросети! Как начать? Отправьте /start нашему боту здесь: @GPTSecurity_Bot 🔘
Мы приглашаем вас подписаться на лайф канал нашего проекта - не упустите это! 🔘 https://t.me/web_security_live
✅ Защита от брута SSH средствами Iptables ЧИТАТЬ Channel | Chat | Live
💻 Анонимность DNS-запросов (кэширование+шифрование) ЧИТАТЬ Channel | Chat | Live
🌐 Как работает SSL шифрование ЧИТАТЬ Channel | Chat | Live
🌟 Большая подборка сервисов с нейросетями. ЧИТАТЬ Channel | Chat | Live
✅ Создаем домашний почтовый сервер ЧИТАТЬ @Web_Security_Channel | Chat
🔒 Защита RDP (Remote Desktop Protocol) ЧИТАТЬ @Web_Security_Channel | Chat
1️⃣2️⃣3️⃣4️⃣5️⃣🚨🔊 Мы рады сообщить вам, что у нас появился эксклюзивный информационно - новостной канал, посвящённый виртуальному миру. 🔘 https://t.me/web_security_live
Showing the 12 most recent of 20 posts we hold for @Web_Security_Channel. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 184,983 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Web Security | Channel” (@Web_Security_Channel), 1,028 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Web_Security_Channel.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.