Channel
@intelxio
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry
7,078subscribers
+80 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001442673452 |
|---|---|
| Type | Channel |
| Username | @intelxio |
| Description | intelx.io - search engine & data archive |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 2 times, most recently 1 November 2026 |
| On Telegram | t.me/intelxio |
Technology — 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 75% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Oct 2026, 02:57 | 7,078 | -3 |
| 25 Oct 2026, 19:59 | 7,081 | +1 |
| 22 Oct 2026, 16:48 | 7,080 | +2 |
| 19 Oct 2026, 06:07 | 7,078 | +8 |
| 16 Oct 2026, 12:28 | 7,070 | -1 |
| 13 Oct 2026, 07:04 | 7,071 | +5 |
| 6 Oct 2026, 17:38 | 7,066 | +6 |
| 29 Sept 2026, 13:58 | 7,060 | +2 |
| 16 Sept 2026, 07:00 | 7,058 | -15 |
| 12 Sept 2026, 02:57 | 7,073 | -3 |
| 7 Sept 2026, 15:19 | 7,076 | +11 |
| 30 Aug 2026, 21:44 | 7,065 | +10 |
| 28 Aug 2026, 01:05 | 7,055 | +11 |
| 24 Aug 2026, 22:17 | 7,044 | +17 |
| 21 Aug 2026, 11:34 | 7,027 | +14 |
| 18 Aug 2026, 01:22 | 7,013 | +9 |
| 14 Aug 2026, 14:36 | 7,004 | +1 |
| 10 Aug 2026, 19:14 | 7,003 | +1 |
| 7 Aug 2026, 19:02 | 7,002 | +4 |
| 7 Aug 2026, 05:00 | 6,998 | first reading |
20 posts held, back to 12 January 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 13 pages 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 12 September 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 3 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
intelx.io and the Identity Portal now support dark mode! We have added a dark mode across all of our websites. And we have just pimped our CAPTCHA system which was previously annoying and hard to read. ➡️ https://blog.intelx.io/2026/09/11/dark-mode/
We just added a new "Export Stealer Log" feature to our Identity Portal! 👏🏻 ➡️ https://blog.intelx.io/2026/02/08/export-stealer-log/
Shame on us! We haven't updated our 3rd party OSINT tools section in years. We updated it, changelog here: ➡️ https://intelx.io/tools?tab=changelog
We just added a new Tree View endpoint to our API: https://help.intelx.io/api/search/#filetreeview
We have added a new category "DNS". It indexes DNS records data such as raw TXT records for domains. It stores already more than 200 million records. ➡️ https://blog.intelx.io/2025/01/12/new-category-dns/
💥 We added a powerful new feature to the Identity Portal: Reverse Lookup You can now search for a domain or URL and get all leaked accounts for a particular service. ➡️ Read more at https://blog.intelx.io/2025/01/03/new-identity-portal-version-%f0%9f%92%a5/
This year we have been busy becoming an SSD-only shop. We will publish soon a blogpost about that journey. We just bought a lot of 16 TB SSDs, some for 2000 EUR a piece. We tested Kioxia SSDs, but they are not as good as the Samsung and UltraStar ones.
We added a new date filter to the Identity Portal. The filters have been improved. More updates are scheduled for January 2025. We are currently working on a reverse search related to Stealer logs.
This is a bit of a wild 🪿 goose chase. Best guess: The vulnerability was around the IPv6 Jumbo Payload parsing. See https://www.rfc-editor.org/rfc/rfc2675.html
What we know: ✅ Code has changed at multiple places in Ipv6pProcessOptions ✅ Looking for integer underflow, thanks to MS disclosure [1] ✅ We have RE'd code versions of patched/unpatched ✅ ChatGPT isn't reliable analyzing it (lol) [1] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38063
Windows Server 2019, tcpip!Ipv6pProcessOptions unpatched (build 6054) vs patched (build 6189):
CVE-2024-38063 Windows TCP/IP Remote Code Execution Vulnerability #reverseengineering #ipv6 #cybersecurity Time to look into this once in 10 years vulnerability!
Showing the 12 most recent of 20 posts we hold for @intelxio. 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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 29 October 2026 — this entry's latest reading, not the date you are reading this.
“Intelligence X” (@intelxio), 7,078 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/intelxio.
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.