Domain monitoring where your team already works
Alerts post to Slack, Discord or your own endpoint. Your code reads the REST API, and your AI assistant connects over MCP.
- Slack messages and Discord embeds
- HMAC-SHA256 signed JSON webhooks
- A REST API and an MCP server
Domainyze connects to other tools in two directions. Alerts are pushed over four channels: email to your account address on every plan, plus a Slack Incoming Webhook, a Discord channel webhook or a generic HTTPS webhook carrying signed JSON, each with its own list of alert types. Your own code pulls through the REST API, which reads and manages the domains you monitor, and AI assistants such as Claude and Cursor connect through the MCP server. There is no Zapier app; a webhook feeds any tool that accepts an HTTP POST.
Where alerts and data go
Alert channels for your team, a REST API for your code, and an MCP server for your AI assistant.
Slack
Alerts post into a Slack channel as Block Kit messages: the alert as a header, its facts as fields, and a button to the domain.
See this integrationDiscord
Alerts arrive in a Discord channel as embeds coloured by severity, titled with the alert and linked to the domain.
See this integrationWebhooks
Every alert as a signed JSON POST to your own HTTPS endpoint, with a stable event name and a documented payload per type.
See this integrationREST API
Read and manage the domains you monitor from your own code, with scoped bearer tokens and one JSON error shape.
See this integrationMCP Server
Let Claude, Cursor or another AI assistant answer questions about your domains from your account, with read-and-add tools and OAuth sign-in.
See this integrationFive monitoring lanes
Each lane answers one question about your domains: the registry record, the DNS zone, the certificate, availability, or the marketplace.
Domain Monitoring
Status, expiry, registrar and transfer lock read straight from the registry, on every domain you own or want, with an alert on every transition.
Explore this laneDNS Monitoring
Per-record diffs on A, MX, NS, TXT and CAA, plus SPF, DKIM and DMARC, read from your authoritative nameservers with a faster lane for delegation changes.
Explore this laneSSL Monitoring
External TLS handshakes that catch a failed ACME renewal your own server believes succeeded, plus chain, hostname coverage and issuer changes, before a browser warning does.
Explore this laneDomain Availability Alerts
Watch a name someone else owns and hear about release the second it happens, tracked through expiry, redemption and pending delete, at standard registration price.
Explore this laneMarketplace & Auction Alerts
The name you are waiting to drop may go to auction instead. Watch the domain marketplace for every name you track and hear the moment one is listed for sale, with the current price and the deadline.
Explore this laneEvery capability, one page each
What is checked, how often, and what fires when it changes. Each one runs inside one of the lanes.
Domain status monitoring
Track lifecycle transitions and the EPP status codes behind them. Get alerted the moment a domain enters grace, redemption or pending delete.
Explore FeatureExpiry monitoring
Renewal reminders on a ladder, checked against the registry rather than your registrar, so a failed auto-renew surfaces while there is still time.
Explore FeaturePortfolio tracking
Every domain you own in one list, whichever registrar holds it, checked for expiry, status, registrar, SSL and DNS changes.
Explore FeatureAlert routing
Route each alert to the place your team already reads: email, Slack, Discord or a signed webhook, one alert per event.
Explore FeatureDNS change detection
Diff the live zone against the one you know, record by record, and confirm every difference on a second resolver before anything fires.
Explore FeatureEmail authentication monitoring
Watch SPF, DKIM and DMARC for the silent edits that cost deliverability, with DKIM selectors discovered from your MX rather than configured.
Explore FeatureDomain watchlists
Put a name you want on a list and be told the moment it frees up, checked harder the closer it gets to release.
Explore FeatureDrop catching
Forecast the day a watched name drops, get a warning before the window opens, and let burst checks catch the release itself.
Explore FeatureRegistration alerts
An alert when a domain registration changes: it becomes available, gets registered, moves registrar or re-points its nameservers.
Explore FeatureMarketplace wantlists
Save a marketplace search once and get a twice-daily digest when new auction and closeout listings match it across GoDaddy, Dynadot and SnapNames.
Explore FeatureStart Monitoring & Catching Domains Today
Join founders, agencies, and domainers already protecting their portfolio. Your first 3 domains are free.
No credit card required • Cancel anytime
Frequently Asked Questions
What the integrations have in common.
Which integrations does Domainyze support?
Slack, Discord and generic HTTPS webhooks for alerts, alongside email; a REST API for your own code; and an MCP server for AI assistants such as Claude, Cursor and VS Code. There is no Zapier app today. A webhook can feed any system that accepts an HTTP POST, including automation tools that expose a catch-hook URL.
Are the integrations included on the free plan?
No. Email alerts are free on every plan; Slack, Discord, webhooks, the REST API and the MCP server are part of the paid plans. Each integration page names the plans that include it.
Should I use webhooks or the API?
Both, for different jobs. A webhook tells your system when something changes, as it happens. The REST API answers what is true now and changes what you monitor. Most integrations receive webhooks and call the API when they need more.
Can I send different alerts to different places?
Yes. Every destination carries its own alert-type filter. You can send DNS and nameserver changes to an engineering Slack channel, renewals to email, and everything to a webhook that writes to your own database.
Will one event arrive more than once?
No. An alert is claimed once per event before any channel delivers it, so a repeated check cannot send it again. A failed delivery is retried, which is the only way the same alert reaches one destination twice, and each attempt is recorded in the delivery log.
How do I know a destination works?
Every destination has a Send test button. It sends a sample alert down the real delivery path, and the result appears in that destination's delivery log.