Any HTTPS endpoint · REST API
DNSai webhooks for DNS changes
Instead of polling, let DNSai push new DNS changes on your domains to your own HTTPS endpoint, Slack relay, ticketing system or automation tool. Every delivery is signed so you can prove it came from DNSai, and you choose which change types to receive.
What webhooks send you
Example answers use made-up domains.
“Email gateway changes only”
Connect in 3 steps (about 5 minutes)
- Open Settings > API Keys > DNS Change Webhooks and add your HTTPS URL.
- Choose the change types and copy the signing secret.
- Verify the signature on each delivery and reply with any 2xx.
Signed-in Enterprise customers get the exact click-by-click steps and ready-to-paste configuration for Webhooks, a one-click API key for it, and a live connection check.
Webhooks requirements: A public HTTPS endpoint (port 443 or 8443). DNSai Enterprise plan.
Good for
- Open a ticket when a customer's MX records change
- Alert sales when a target account switches email gateway
- Stream DNS changes into a SIEM without polling
Security
- Requests use HTTPS with an API key in the Authorization header. Give each system its own key with an expiry, and an IP allowlist for your own servers.
- Account and organization owners can make API keys and assistants read-only, so they can read your data but never change it or start scans.
- Starting a credit-spending Deep Scan always needs an estimate and your explicit confirmation.
- DNSai data comes from public DNS and web records. Your watchlists, notes and tags stay private to your account and are only shared with an AI tool you connect yourself.
Connect Webhooks to DNSai
The API and AI connectors are included with DNSai Enterprise plans. Every member of your organization shares one set of limits, and every call counts from the first one.
Other integrations
Last checked 2026-10-30.