Webhook alerts for
SSL, DNS & uptime monitoring
Route monitoring alerts to your own endpoint as JSON.
How it works
How Merlonix delivers to Webhook
Merlonix POSTs a structured JSON payload to any HTTP endpoint you own. Point it at your own automation, ticketing system, SIEM, or an internal bridge and handle the alert however you like — the generic webhook is the escape hatch when a purpose-built channel isn’t enough.
A structured JSON body carries the asset, the check that fired, the before/after, severity, and timestamp — parse and route it however you need.
Bridge monitoring into an internal tool, a ticket queue, or a log pipeline without waiting for a native integration.
One asset can fan alerts to a webhook and a human channel at the same time.
Setup
Set up Webhook in three steps
Step 1
Stand up an HTTP endpoint that accepts a POST with a JSON body.
Step 2
In Merlonix, add a Webhook notification channel with the endpoint URL.
Step 3
Send the one-click test, confirm your endpoint parsed it, then attach the channel to your assets.
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
Webhook 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 Webhook alerts?
Webhook alert delivery is available on Starter and above. You can start on the free plan and add Webhook when you are on the qualifying tier.
What do Webhook 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 Webhook message carries that same context, so a responder can triage from the alert itself.
Can I use Webhook alongside other channels?
Yes. A single asset can send to Webhook 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 Webhook channel just decides where the resulting alert is delivered.
Wire monitoring into Webhook today
SSL, DNS, uptime, and vendor-aware alerts across every client asset — delivered where your team already works. Start free, no credit card.