Telegram RegisterThe public register of Telegram
Telegram profile photo for Canal de Who is secure

Channel

Canal de Who is secure

@canalwhoissecure

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

124subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001158682287
TypeChannel
Username@canalwhoissecure
CreatedBetween 1 March 2018 and 2 November 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 November 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/canalwhoissecure

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 8 October 2026 and assigned it the closest of 31 fixed categories, at 89% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

124127125.56 August 2026 — 127 subscribers9 August 2026 — 127 subscribers20 August 2026 — 126 subscribers8 October 2026 — 124 subscribers16 October 2026 — 125 subscribers7 November 2026 — 124 subscribers6 August 20267 November 2026
6 measurements spanning 92 days, net -3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 124–127 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Nov 2026, 02:16124-1
16 Oct 2026, 11:39125+1
8 Oct 2026, 11:37124-2
20 Aug 2026, 13:53126-1
9 Aug 2026, 02:02127no change
6 Aug 2026, 20:46127first reading

Engagement

20 posts held, back to 2 November 2020 — 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 page of 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 15 May 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 1 post, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
😍150.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 3 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 2 November 2020 to 15 May 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

15 May 2025, 22:44 UTC164 views2 reactionsread 9 August 2026

Nueva entrada ❗️ Sigo vivo y he hecho una nueva publicación. Se trata de la resolución de un reto web que hice para el CTF de Var Group España para RootedCon 2025. Espero que os guste. https://www.whoissecure.xyz/2025/05/rootedcon-2025-var-store.html

❤1😍1

19 May 2023, 20:38 UTC768 views0 reactionsread 9 August 2026

Nueva entrada ❗ He escrito una entrada en la que os presento Yaset, una herramienta para enumeración pasiva de subdominios basada en plantillas que he escrito. Espero que os guste! 📎 https://www.whoissecure.xyz/2023/05/yaset.html

16 Apr 2023, 11:32 UTC578 viewsread 9 August 2026

Nueva entrada ❗ Hoy traigo otro CVE en una librería anti-SSRF, esta vez en Golang ¡Espero que os guste! 📎 https://www.whoissecure.xyz/2023/04/cve-2023-24623.html

30 Jan 2023, 22:07 UTC612 viewsread 9 August 2026

Nueva entrada ❗ ¡Hola! He publicado una entrada en la que os enseño un CVE que he encontrado en una librería anti-SSRF de python. ¡Espero que os guste! 📎 https://www.whoissecure.xyz/2023/01/cve-2023-24622-y-mas.html

31 Dec 2022, 00:11 UTC≈5,980 viewsread 9 August 2026

Nueva entrada ❗ Para cerrar el año os traigo una extensión para Burp Suite que he publicado y que sirve para generar wordlists basados en tu historial. Espero que os guste la entrada y que os sea útil la extensión :) 📎 https://www.whoissecure.xyz/2022/12/burp-wordlist-generator-primera-extension-burp.html

26 Oct 2022, 21:54 UTC836 viewsread 9 August 2026

Nueva entrada ❗️ ¡Buenas! He escrito la solución al reto Frasco de galletas de Una al Mes (@uamctf). Espero que os guste :) 📎 https://www.whoissecure.xyz/2022/10/una-al-mes-frasco-de-galletas.html

12 Jul 2022, 12:26 UTC429 viewsread 9 August 2026

📢📢📢 Anunciamos de forma oficial que el próximo 29 de Octubre de celebraran las jornadas BitUp Alicante 2022 en formato presenciales! 🎊🎊🎊 ✅ Se realizaran en el Auditorio del Edificio Puerta Ferrisa ( C/ Jorge Juan 21, Alicante ). 🏬⛪️ ✅ Iremos dando novedades! Por ahora abrimos Call4Papers, para quien quiera mostrar sus proyectos, ideas, charlas interesante... 👀👀 Las temáticas dentro del ámbito de la seguridad info…

1 Jun 2022, 00:13 UTC288 viewsread 9 August 2026

Nueva entrada ❗️ ¡Hola! He resuelto la máquina All in One de TryHackMe y os dejo aquí la solución. Espero que os guste 😁 📎 https://www.whoissecure.xyz/2022/06/tryhackme-all-in-one.html

17 Mar 2022, 19:19 UTC611 viewsread 9 August 2026

Nueva entrada ❗️ ¡Buenas! He escrito la solución al segundo reto de Damn Vulnerable DeFi, Naive receiver, para seguir con la serie de DeFi hacking. Espero que os guste. 📎 https://whoissecure.blogspot.com/2022/03/defi-hacking-2-naive-receiver-dvdf.html

14 Mar 2022, 21:42 UTC641 viewsread 9 August 2026

Nueva entrada ❗️ ¡Hola a todos! Hoy os traigo una entrada sobre DeFi hacking. Vamos a resolver el primer reto de Damn Vulnerable DeFi, Unstoppable. En él vamos a ver cómo dejar inservible la función de flash loans de este smart contract. 📎 https://whoissecure.blogspot.com/2022/03/defi-hacking-1-unstoppable-dvdf.html

20 Jan 2022, 01:09 UTC622 views0 reactionsread 9 August 2026

Nueva entrada ❗️ ¡Buenas! Después de tanto tiempo os traigo una nueva entrada. En esta ocasión se trata de la resolución de Raz0rBlack, una máquina de directorio activo de TryHackMe. Espero que os guste. 📎 https://whoissecure.blogspot.com/2022/01/tryhackme-raz0rblack.html

29 Oct 2021, 05:44 UTC576 viewsread 9 August 2026

Nueva entrada ❗ ¡Buenos días! He escrito una entrada sobre mi primer CVE. Cómo ha sido buscarlo, reportarlo y conseguirlo. 📎 https://whoissecure.blogspot.com/2021/10/cve-2021-41728-o-como-he-conseguido-mi.html

Showing the 12 most recent of 20 posts we hold for @canalwhoissecure. 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.

Cite this entry

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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“Canal de Who is secure” (@canalwhoissecure), 124 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/canalwhoissecure.

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.