Channel
@IRSentinels
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,025subscribers
+1,002 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1004354987743 |
|---|---|
| Type | Channel |
| Username | @IRSentinels |
| Created | Between 1 June 2026 and 19 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 5 September 2026 |
| On Telegram | t.me/IRSentinels |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 02:28 | 4,025 | +2 |
| 30 Aug 2026, 12:14 | 4,023 | -2 |
| 27 Aug 2026, 04:57 | 4,025 | -1 |
| 24 Aug 2026, 10:06 | 4,026 | -2 |
| 20 Aug 2026, 20:46 | 4,028 | -1 |
| 17 Aug 2026, 19:43 | 4,029 | +2 |
| 15 Aug 2026, 01:48 | 4,027 | +1,005 |
| 11 Aug 2026, 08:42 | 3,022 | -1 |
| 8 Aug 2026, 12:38 | 3,023 | no change |
| 8 Aug 2026, 10:02 | 3,023 | first reading |
19 posts held, back to 19 July 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 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 19 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
563 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 71.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 405 | 71.9% | |
| 👍 | 63 | 11.2% | |
| 👏 | 48 | 8.53% | |
| 🔥 | 47 | 8.35% |
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 19 of the 19 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 563 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 19 July 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
✎ Bypass 403 Forbidden with HTTP Headers Fuzzing I’ve analyzed numerous tools, blogs, tweets, and other resources on bypassing #403 #Forbidden errors using HTTP Headers #Fuzzing techniques. After extensive research, I’ve compiled a list of headers you can fuzz to potentially #bypass 403 restrictions. • HTTP Headers List: GitHub #bugbounty #403bypass #HTTP ⭐️@IRSentinels
❤31
✎ Common Rate Limit Bypass Techniques IP Spoofing Altering a request’s source IP to appear from another device, and rotating IPs lets an attacker bypass per-IP limits. You can use the following Burp Extensions for IP Spoofing: • BurpFakeIP: GitHub • IP-Rotate: GitHub Changing User-Agent Rate-limit systems often track the User-Agent header; changing or randomizing it makes requests appear from different clients, an…
👏17❤16👍15🔥8
✎ Burp Extension for API Testing in JS-Rich Targets This tool helps identify endpoints, files, internal emails, and some secrets hidden in minified JavaScript, achieving maximum efficiency while minimizing noise in the results. • Repository: Github #bugbounty #recon #javascript #burp ⭐️@IRSentinels
❤1
✎ IP Spoofing to Account Takeover: You Patched It? Really? In my previous article, I described how I found a security flaw in a popular desktop app's OAuth flow that allowed me to steal any user's account with just one click. I reported it, saw it patched, and then bypassed the patch again. Since the process of bypassing and exploiting the flaw is interesting to me, I decided to write a second article about it. • B…
❤23🔥23👍19👏14
Exploiting HTTP Parser Inconsistencies: ACL Bypasses, SSRF, and Cache Poisoning Original text: “Exploiting HTTP Parsers Inconsistencies” — Rafa, Rafa’s Security Researches (research conducted December 2021 – April 2022). Code blocks, tables and figures below are reproduced verbatim with attribution captions. Executive Summary HTTP is the connective tissue of the modern web, but the specification leaves enough ambi…
👍16👏12🔥11❤8
🗒 File Upload Vulnerabilities — Attacker's Cheat Sheet Offensive checklist for testing upload endpoints — from filename tricks to full RCE. Filename attacks: SSRF via filename, RTLO extension spoofing, XSS/SQLi/RCE/LFI payloads in filename Extension/MIME bypass: double extensions, case mixing, null byte injection, special chars, duplicate Content-Type/filename fields Content exploitation: ImageTragick (RCE/…
❤1
CVE-2026-41940 cPanel and WHM versions after 11.40 contain an authentication bypass vulnerability in the login flow that allows unauthenticated remote attackers to gain unauthorized access to the control panel.
❤55
MCP Client OAuth Refresh-Token Support Matrix (June 2026) https://redcaller.com/docs/references/mcp-client-oauth-refresh-token-support
❤45
How Can Found a Critical OAuth Misconfiguration That Led to Account Takeover https://medium.com/@iamshafayat/how-i-found-a-critical-oauth-misconfiguration-that-led-to-account-takeover-abfec43eaea6
❤50
MeshCentral: From XSS to RCE https://techanarchy.net/meshcentral-from-xss-to-rce/
👍13❤10👏5🔥5
How to use Claude Code for Bug Bounty: find fast, validate manually https://www.yeswehack.com/learn-bug-bounty/llm-series-claude
❤1
https://x.com/wadgamaraldeen/status/2079244138541711720?s=52
❤1
Showing the 12 most recent of 19 posts we hold for @IRSentinels. 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.
Named by 1 registered channel — 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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“IRSentinel” (@IRSentinels), 4,025 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/IRSentinels.
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.