🚨 El CCN avisa de una actualización de seguridad para #Apache HTTP Server que resuelve una vulnerabilidad crítica. Se recomienda actualizar inmediatamente y aplicar medidas de mitigación Más info 👉https://t.co/LuHeyUY0Se https://t.co/rZwVueP5AM — Centro Criptológico Nacional (@CCNCERT) Nov 12, 2026

Channel
CCN
@CCNCERT
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cross-platform identity · Cite this entry
6,877subscribers
+182 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001385811594 |
|---|---|
| Type | Channel |
| Username | @CCNCERT |
| Description | Capacidad de Repuesta a Incidentes del Centro Criptológico Nacional que, como CERT Gubernamental Nacional, contribuye a reforzar la ciberseguridad en España. |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/CCNCERT |
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 12 September 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 22:17 | 6,877 | +6 |
| 8 Nov 2026, 03:07 | 6,871 | +6 |
| 5 Nov 2026, 08:49 | 6,865 | +3 |
| 2 Nov 2026, 17:19 | 6,862 | +4 |
| 30 Oct 2026, 15:20 | 6,858 | +8 |
| 27 Oct 2026, 13:39 | 6,850 | +8 |
| 24 Oct 2026, 03:58 | 6,842 | +27 |
| 20 Oct 2026, 18:17 | 6,815 | +4 |
| 17 Oct 2026, 19:30 | 6,811 | +8 |
| 15 Oct 2026, 00:27 | 6,803 | +5 |
| 11 Oct 2026, 16:20 | 6,798 | +9 |
| 5 Oct 2026, 00:38 | 6,789 | +7 |
| 25 Sept 2026, 17:40 | 6,782 | +18 |
| 15 Sept 2026, 07:38 | 6,764 | +6 |
| 11 Sept 2026, 09:01 | 6,758 | +17 |
| 6 Sept 2026, 04:16 | 6,741 | -4 |
| 2 Sept 2026, 01:38 | 6,745 | +4 |
| 27 Aug 2026, 06:17 | 6,741 | +8 |
| 24 Aug 2026, 02:48 | 6,733 | +7 |
| 20 Aug 2026, 02:18 | 6,726 | first reading |
Engagement
48 posts held, back to 23 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 32.9%
- avg views ÷ 6,877 subscribers
- Avg views / post
- 2,260
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 48 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 12 November 2026 |
|---|---|
| Posts held | 48 (23 June 2026 – 12 November 2026) |
| Views total | 45,290 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 16:27 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈1
- Links
- ≈2,900
Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🔐 El CCN publica 25 nuevas guías y actualiza otras 9 de la serie CCN-STIC 1000 sobre Procedimientos de Empleo Seguro (PES) de productos y servicios TIC: Identidad, detección y respuesta, redes, nube y móviles. Más info 👉 https://t.co/6aFpSKxaEC #CCNSTIC #Ciberseguridad https://t.co/ETdDwVjnMj — Centro Criptológico Nacional (@CCNCERT) Nov 12, 2026
@Accenture, @opennac, #CSA, @DotForce_Spain, @googlecloud, @IndraCompany, @Procesia1, @Telefonica, #TRC y @Yubico: patrocinadores estratégicos de las XX Jornadas STIC Un espacio para sumar capacidades. #STIC2026 #Patrocinadores #Estratégico 🔗 jornadas.ccn-cert.cni.es/es/xxjornadas
La IA abre nuevas posibilidades pero, ¿qué implica su uso ofensivo y por qué es clave comprenderlo? Una aproximación a uno de los conceptos centrales de las XX Jornadas STIC. 👇 https://t.co/nngEVVnUzU https://t.co/Np6675CHiI — Centro Criptológico Nacional (@CCNCERT) Nov 6, 2026
Las XX Jornadas STIC cuentan con @IZERTIS y @s2grupo como patrocinadores VIP. Dos compañías que se suman a una cita clave para compartir conocimiento y fortalecer la cooperación en ciberseguridad. #STIC2026 #Patrocinadores #VIP https://t.co/SCzTa1Nd4Q — Centro Criptológico Nacional (@CCNCERT) Nov 5, 2026
🤝 3 nuevas entidades en la Red Nacional de SOC 🏛️Públicas: @CSUC_info 🏣Proveedoras: @inforges y #DMNTR Network Solutions Ya son 344 las entidades adheridas que, en octubre, compartieron más de 30.200 eventos Más info 👉https://t.co/23sWdEgfKm https://t.co/bKyKaUAZxa — Centro Criptológico Nacional (@CCNCERT) Nov 5, 2026
📘 El CCN facilita a las 618 entidades que han participado en la autoevaluación sobre preparación ante #IAOfensiva, un Plan de Acción con 53 iniciativas. Destacan: parcheo de vulnerabilidades, MFA resistente al phishing y control cadena de suministro 👉https://t.co/TNWWrfGADO https://t.co/Oy9Kja9W5T — Centro Criptológico Nacional (@CCNCERT) Nov 3, 2026
La estrategia 'Cosecha Ahora, Descifra Después' muestra la necesidad de prepararse frente a los riesgos de la computación cuántica.🔐 En las XX Jornadas #STIC2026 habrá ponencias sobre esta amenaza y sus implicaciones en la protección de la información🔗https://t.co/nngEVVnUzU https://t.co/RH6it1Fu4x — Centro Criptológico Nacional (@CCNCERT) Oct 30, 2026
🚀Nueva metodología del CCN para evaluación de seguridad de productos con inteligencia artificial recogida en la #GuíaCCNSTIC_2011 Establece un marco común para que fabricantes y organismos puedan confiar en la seguridad de los productos con IA Más info👉https://t.co/QwlP4NgDwg https://t.co/vEhYH7TAsX — Centro Criptológico Nacional (@CCNCERT) Oct 29, 2026
📢 El CCN renueva su herramienta de Gobernanza INÉS con el fin de facilitar la adecuación al ENS y consolidar la información de ciberseguridad de los organismos públicos. Las novedades se presentarán en las próximas #STIC2026 -Sala 6- Más info 👉https://t.co/vH75nwhMgj https://t.co/v9ehhWI8gp — Centro Criptológico Nacional (@CCNCERT) Oct 28, 2026
El CCN incorpora 4 nuevos productos y 1 servicio al catálogo #CPSTIC de octubre en las categorías de: protección de redes y sistemas, protección de la información, de dispositivos y perímetro y un servicio de control de accesos. Más info 👉https://t.co/jM72oSibTD https://t.co/bG9rrcbNYT — Centro Criptológico Nacional (@CCNCERT) Oct 27, 2026
🆙El CCN actualiza su #GuíaCCN_STIC 106, que establece el procedimiento para incorporar soluciones a su Catálogo CPSTIC, tanto en el listado de cualificados como en el de Conformidad y Gobernanza. Más info 👉https://t.co/NnuFEVUf8C https://t.co/8R8gBN5l2Z — Centro Criptológico Nacional (@CCNCERT) Oct 26, 2026
Showing the 12 most recent of 48 posts we hold for @CCNCERT. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
- Dead references
- 4
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 4
- vacant every time we have ever looked
@CCNCERT named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 8 August 2026 – 9 August 2026
named in 2 posts, 8 August 2026 – 9 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@policianacional · 19,337
Telegram ranks this channel #6 of 87 here — alongside 86 others — read 2 October 2026
@seguridadinformatic4 · 29,192
Telegram ranks this channel #7 of 76 here — alongside 75 others — read 8 September 2026
@ciudadanosdeuniforme · 28,934
Telegram ranks this channel #10 of 76 here — alongside 75 others — read 9 September 2026
@Viajerospiratas · 66,650
Telegram ranks this channel #20 of 47 here — alongside 46 others — read 29 August 2026
@forocoches_oficial · 41,913
Telegram ranks this channel #26 of 58 here — alongside 57 others — read 29 August 2026
@getmanfred · 18,898
Telegram ranks this channel #35 of 73 here — alongside 72 others — read 4 October 2026
@cybdetective · 28,057
Telegram ranks this channel #42 of 49 here — alongside 48 others — read 11 September 2026
@thehackernews · 165,587
Telegram ranks this channel #44 of 58 here — alongside 57 others — read 13 August 2026
@SPE112 · 25,049
Telegram ranks this channel #48 of 75 here — alongside 74 others — read 15 September 2026
@cibsecurity · 29,268
Telegram ranks this channel #54 of 58 here — alongside 57 others — read 10 September 2026
@StarkPrivacy · 19,841
Telegram ranks this channel #58 of 75 here — alongside 74 others — read 30 September 2026
@xataka · 48,826
Telegram ranks this channel #67 of 86 here — alongside 85 others — read 25 August 2026
@TokinPrivacy · 49,625
Telegram ranks this channel #76 of 86 here — alongside 85 others — read 25 August 2026
@eldiarioes · 44,720
Telegram ranks this channel #78 of 92 here — alongside 91 others — read 28 August 2026
This channel appears in 14 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cross-platform identity — Wikidata
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | No label recorded on this Wikidata item |
|---|---|
| X / Twitter | @CcnCert |
| Official site | https://www.ccn-cert.cni.es |
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“CCN” (@CCNCERT), 6,877 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/CCNCERT.
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.