Telegram RegisterThe public register of Telegram
Telegram profile photo for Code Signing Certificates

Channel

Code Signing Certificates

@evcodeservices

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

379subscribers

+75 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003767705078
TypeChannel
Username@evcodeservices
Created4 February 2026 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live10 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/evcodeservices

Topic

Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 47% 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 why it has no browse page of its own yet.

Growth

304379341.57 August 2026 — 304 subscribers8 August 2026 — 304 subscribers15 August 2026 — 314 subscribers22 August 2026 — 320 subscribers29 August 2026 — 323 subscribers8 September 2026 — 339 subscribers15 September 2026 — 341 subscribers30 September 2026 — 365 subscribers10 October 2026 — 379 subscribers7 August 202610 October 2026
9 measurements spanning 64 days, net +75. 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 293–390 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 08:57379+14
30 Sept 2026, 08:36365+24
15 Sept 2026, 16:17341+2
8 Sept 2026, 12:18339+16
29 Aug 2026, 11:35323+3
22 Aug 2026, 13:18320+6
15 Aug 2026, 08:45314+10
8 Aug 2026, 07:50304no change
7 Aug 2026, 19:14304first reading

Engagement

7 posts held, back to 4 February 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 7 posts for this entry, the most recent from 15 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

15 May 2026, 07:48 UTC902 viewsread 8 August 2026

➕ Also, professionals with experience and knowledge in certificate and file warm-up can reach out to me for business. Contact: @Demonizacija / @digicert @sectigo @globalsign @sslcom

Signed Ezekiel

15 May 2026, 07:46 UTC885 viewsread 8 August 2026

For now, I'm not providing a 100% SmartScreen bypass guarantee, but until the Artifact Signing adjustment is completed, I'm continuing to sell EV/OV certificates. And Microsoft Artifact Signing certificates. Since EV and OV Code Signing certificates have now been brought down to the same level, you can purchase an OV Code Signing certificate and try to build up reputation yourself through warm-up. There's no other a…

Signed Ezekiel

15 May 2026, 07:45 UTC737 viewsread 8 August 2026

❓ Update on EV Code Signing Certificates – May 6, 2026 Hello, following the latest update, the article was updated again on May 6. There was also another article that was modified during the April update. According to this, all distributions outside of the Microsoft Store even those signed with Microsoft Artifact Signing, meaning Microsoft's own code signing certificate will trigger or not trigger a SmartScreen warn…

28 Apr 2026, 06:08 UTC846 viewsread 8 August 2026

⚠️ Major Change to EV Code Signing Certificates – April 17, 2026 Hello, there was a rule that originally came into effect in 2024, and Microsoft updated the article containing this rule again on April 17, 2026. According to this update, EV Code Signing certificates are no longer sufficient on their own for SmartScreen Bypass. In other words, in terms of how they function, they now have the same authority as OV certi…

14 Feb 2026, 17:44 UTC≈1,130 viewsread 8 August 2026
Photo

🛡 EV Code Signing Certificate Services You can bypass the Windows SmartScreen warning by signing your files with extensions such as .exe .msi .dll .cab .ocx .xpi .xap. For your software like ScreenConnect, a normal screen appears without warnings instead of red (malicious) or yellow (unsigned / Unknown Publisher) UAC warnings. We are also open to custom name requests for the "Verified Publisher" section appearing i…

Showing the 7 most recent of 7 posts we hold for @evcodeservices. 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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“Code Signing Certificates” (@evcodeservices), 379 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/evcodeservices.

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.