Email and Webhook Integrations
Domainyze aims to provide flexible notification options to ensure you receive critical alerts in the most convenient way possible.
Domain Email Alerts
- Primary Channel: Currently, all alerts and notifications from Domainyze are sent to the email address associated with your account.
- Ensuring Delivery: Please ensure
noreply@domainyze.comis whitelisted in your email client to prevent alerts from going to spam. - Update Email: You can update your primary account email in your profile settings.
Domain Webhook Alerts
-
Integration Made Easy: Webhooks provide a powerful way to integrate Domainyze alerts into your existing systems (e.g., Slack, custom dashboards, ticketing systems, monitoring tools).
-
How to Enable:
- Navigate to your User Settings
- Enable the "Webhook Notifications" toggle
- Enter your webhook URL (the endpoint where you want to receive notifications)
- Save your settings
-
How it Works: When a domain alert is triggered, Domainyze will send an HTTP POST request to your configured webhook URL with the alert details in JSON format. Only
http/httpsURLs on standard ports (80/443) are supported. -
Webhook Payload: Each webhook notification includes comprehensive information about the triggered alert, including domain details, alert type, status changes, and timestamps.
-
Security: Your webhook endpoint receives a unique secret key. Each request includes an
X-Webhook-Signatureheader containing an HMAC-SHA256 of the raw request body, computed with your secret.
Verifying the signature
Compute HMAC-SHA256(rawRequestBody, yourSecret) and compare it to the X-Webhook-Signature header. You must hash the exact bytes of the request body as received — do not re-serialize the parsed JSON before hashing.
$expected = hash_hmac('sha256', $request->getContent(), $yourSecret);
$valid = hash_equals($expected, $request->header('X-Webhook-Signature'));
Breaking change (verification): Signatures are now computed over the exact raw body bytes we send. If your receiver previously re-encoded the parsed JSON (e.g.
hash_hmac('sha256', json_encode($parsed), $secret)) before comparing, switch to hashing the raw received body. This avoids intermittent mismatches caused by slash/unicode escaping differences.
SMS (Planned/External Integration)
- Future Enhancement: We understand the importance of receiving critical alerts via SMS for immediate attention. SMS notifications are currently a planned feature.
- External Integration: In the meantime, you can use our Webhook support to send alerts to third-party services like Twilio or Zapier to trigger SMS notifications on your own.
- Native Support: We are actively exploring native SMS integration for future updates.
We are continuously working to expand our notification capabilities to meet the diverse needs of our users.