Telegram alerts for
SSL, DNS & uptime monitoring
Mobile-push monitoring alerts to a Telegram chat — no SMS cost.
How it works
How Merlonix delivers to Telegram
Merlonix sends alerts through a Telegram bot to the chat or group you specify. Provide the bot token and chat id in a Merlonix notification channel and each alert arrives as a Telegram message — mobile push on your phone without the per-message cost of SMS.
Mobile push notifications without SMS charges — useful for a solo operator or a small on-call group.
Send to a private chat or a shared group so the whole team sees the same alert.
The message carries the asset, the check that fired, and the change, like every other channel.
Setup
Set up Telegram in three steps
Step 1
Create a Telegram bot with @BotFather and copy its token.
Step 2
Start a chat (or add the bot to a group) and get the chat id.
Step 3
In Merlonix, add a Telegram notification channel with the token and chat id, then test.
What fires an alert
The delivery channel changes; the monitoring doesn’t
Every alert carries the same context regardless of destination: which client asset changed, which check fired (SSL-certificate expiry or change, DNS-record drift, domain registration/expiry, uptime, DNSSEC, security headers, blocklist status, and more), and what specifically changed. Alerts fire on real state changes between definitive checks — not on a transient blip.
- SSL / TLS monitoring
- DNS & DNSSEC monitoring
- Domain-hijack & registrar-lock monitoring
- Security-header monitoring
Telegram is one of ten delivery destinations, and Merlonix also runs on-call rotations and escalation policies so the right person is paged. See alerting & on-call →
Other destinations
Prefer a different channel?
Merlonix delivers the same alerts to every destination your team already uses.
Common questions
Frequently asked questions
Which Merlonix plan includes Telegram alerts?
Telegram alert delivery is available on Starter and above. You can start on the free plan and add Telegram when you are on the qualifying tier.
What do Telegram alerts actually contain?
Every alert carries the same context regardless of destination: which client asset changed, which check fired (SSL-certificate expiry or change, DNS-record drift, domain registration/expiry, uptime, DNSSEC, security headers, blocklist status, and more), and what specifically changed. Alerts fire on real state changes between definitive checks — not on a transient blip. The Telegram message carries that same context, so a responder can triage from the alert itself.
Can I use Telegram alongside other channels?
Yes. A single asset can send to Telegram and other destinations at once — for example email plus a chat channel plus an on-call channel — so no alert rides on one delivery path. Merlonix supports email, Slack, Microsoft Teams, Discord, Telegram, Google Chat, a generic webhook, SMS, PagerDuty, and Opsgenie.
Do I need access to my clients’ servers to monitor them?
No. Merlonix probes each domain from the outside in — its public SSL certificate, DNS records, registration data, and HTTP responses — the same way a browser or resolver would. You add an asset by hostname; the Telegram channel just decides where the resulting alert is delivered.
Wire monitoring into Telegram today
SSL, DNS, uptime, and vendor-aware alerts across every client asset — delivered where your team already works. Start free, no credit card.