Outbound webhooks

Plan availability

Webhooks is available on Pro and Business. See the plan comparison.

Outbound webhooks send DomainDash events to your own systems as they happen, so you can connect DomainDash to Zapier, Make, n8n, or your own infrastructure.

What outbound webhooks are

A webhook is an HTTP request DomainDash sends to a URL you choose when an event you've subscribed to happens, so you don't need to poll for changes. When a site goes down or recovers, or a certificate is about to expire, DomainDash sends a signed POST request to your endpoint with the details.

Each event arrives as a JSON payload with a type (like site.went_down), a timestamp, and a data object describing what happened.

Adding an endpoint

You manage webhooks on Settings → Developers. To add one, choose Add endpoint and fill in:

• URL — the address DomainDash should send events to. It must be an HTTPS URL.
• Description — an optional label to remind you what the endpoint is for, for example "Zapier integration".
• Events — the events you want this endpoint to receive (see below).

You can add more than one endpoint and subscribe each to a different set of events, for example one endpoint for incident events and another for expiry warnings.

Choosing which events to subscribe to

Each endpoint only receives the events you subscribe it to. There are eleven events, grouped by category. The code after each name is the type in the payload.

Sites

• Site added (site.added) — a new site was added to the team.

Incidents

• Site went down (site.went_down) — a site became unreachable.
• Site recovered (site.recovered) — a site came back online after being unreachable.

SSL

• SSL certificate expiring (ssl.expiring) — a site's SSL certificate is approaching expiry.
• SSL certificate expired (ssl.expired) — a site's SSL certificate has expired.
• SSL certificate renewed (ssl.renewed) — a site's SSL certificate was renewed.

Domain

• Domain expiring (domain.expiring) — a site's domain registration is approaching expiry.
• Domain expired (domain.expired) — a site's domain registration has expired.
• Domain renewed (domain.renewed) — a site's domain registration was renewed.

DNS

• DNS resolution failing (dns.failing) — a site's DNS resolution started failing.
• DNS resolution restored (dns.restored) — a site's DNS resolution was restored.

DomainDash doesn't send an event for a failed content check, an invalid certificate or a slow response. Their recoveries do send events: a content check passing again and an incident for a site responding slowly resolving both send site.recovered, and an invalid certificate being fixed sends ssl.renewed.

To change which events an endpoint is subscribed to, edit it.

The signing secret

When you create an endpoint, DomainDash generates a unique signing secret that starts with whsec_. It appears in a banner at the top of the page, right after you save the endpoint.

Copy your signing secret straight away

DomainDash shows the signing secret only once, when you create the endpoint or rotate the secret. It stores the secret encrypted and can't show it to you again. Copy it into your secrets manager before you leave the page.

You use the signing secret to verify that an incoming request came from DomainDash and wasn't tampered with on the way.

Rotating the secret

To replace the secret (for example if it might have leaked), use Rotate secret in the endpoint's menu. DomainDash generates a new whsec_ secret and shows it once. Your old secret stops working immediately, so update your endpoint to use the new one straight away.

Verifying the signature

DomainDash signs every delivery using the Standard Webhooks scheme. Each request includes three headers:

• webhook-id — a unique ID for the event.
• webhook-timestamp — when the event was sent.
• webhook-signature — the signature, computed from your signing secret.

Your endpoint should verify the signature before trusting the payload. Standard Webhooks is an open standard, so you can use any Standard Webhooks library in your language of choice. Pass it your whsec_ signing secret and the three headers, and it confirms the request is authentic.

Sending a test event

To check your endpoint is wired up correctly, use Send test event from the endpoint's menu. DomainDash queues a webhook.test event and sends it to your URL, signed like a real event. Watch it arrive in recent deliveries and confirm your endpoint accepted it.

Who can manage webhooks

The team owner and admins manage webhooks. Members can't add, edit, or delete endpoints. Managing webhooks also requires a plan that includes the feature. If your plan doesn't, you'll see an upgrade prompt in place of the management screen.

Frequently asked questions

Can I send different events to different endpoints?

Yes. You can add more than one endpoint and subscribe each to a different set of events, for example one endpoint for incident events and another for expiry warnings. To change which events an endpoint receives, edit it.

What happens if I lose my signing secret?

DomainDash shows the signing secret only once and can't show it again. If you lose it or it might have leaked, use Rotate secret in the endpoint's menu. DomainDash generates a new whsec_ secret and shows it once. Your old secret stops working immediately, so update your endpoint straight away.

How do I verify a webhook came from DomainDash?

DomainDash signs every delivery using the Standard Webhooks scheme, with webhook-id, webhook-timestamp, and webhook-signature headers. Pass your whsec_ signing secret and the three headers to any Standard Webhooks library, and it confirms the request is authentic before you trust the payload.

Who can manage webhooks?

The team owner and admins, on a plan that includes webhooks. Members can't add, edit, or delete endpoints. If your plan doesn't include webhooks, you'll see an upgrade prompt in place of the management screen.

Related

• Deliveries and retries for what happens after an event is sent
• How incidents work for the events that trigger webhooks
• Notification channels for the other ways DomainDash can alert you
• Plans and pricing for which plans include webhooks