# Monitoring

Monitors check a domain, a certificate, DNS records or a web page on a schedule and tell you when something
changes. Checks are included in your plan and never use credits. Create monitors under **Monitors** in your
dashboard, through the REST API (`/v1/monitors`), or from an AI assistant with the `create_monitor` MCP tool.

## What you can monitor

| Monitor | Watches | How often |
| --- | --- | --- |
| Domain expiry | The registration: expiry date, registrar, nameservers, transfer lock | Daily |
| SSL | The certificate: expiry, trust, the host name, the issuer | Daily |
| DNS | The records you choose (A, AAAA, CNAME, MX, NS, TXT, CAA and more) | Every 15 minutes or hourly |
| Uptime | A URL answers with a working page, optionally containing a keyword | Every minute or every 5 minutes |
| Page change | The visible text of a page, or of one part of it | Hourly or daily |
| Score drop | The score of the email checker, security headers check or SEO audit | Daily or weekly |
| Lookalike domains | Newly registered domains that look like yours | Daily |

The Free plan includes 3 monitors for domain expiry and SSL. The Monitor, Pro and Agency plans add the other
kinds, shorter intervals and more monitors; your dashboard shows how many your plan includes and how many are in
use. If a plan change leaves you with more monitors than the plan includes, the oldest keep running and the rest
pause until you delete some or upgrade.

## The first check

The first check runs as soon as you create a monitor. It records how things are now (the baseline) and doesn't
alert, except for a deadline that is already close: a domain or certificate that expires within 60 days is
reported at once.

## What counts as a change

Monitors are built to stay quiet unless something real happens:

- **DNS**: a different set of values for a name and record type. TTL changes and a different order never count.
- **Domain expiry**: reminders 60, 30, 14, 7 and 1 days before the expiry date and when it passes, a renewal,
  and a change of registrar, nameservers or transfer lock.
- **SSL**: reminders 30, 14, 7 and 1 days before expiry, problems such as a name mismatch, and a new
  certificate. Sites that switch between two certificates don't raise an alert each time.
- **Uptime**: the site going down and coming back, with how long it was down, and slow answers when you set a
  limit.
- **Page change**: different text, with a short excerpt of what changed. Choose **Ignore numbers** for pages
  with counters or dates, or list lines to ignore.
- **Score drop**: new failing findings, and the score falling below the minimum you set.
- **Lookalike domains**: each newly registered lookalike, with how risky it looks.

## Confirmed before you're alerted

A change that could be a blip is checked again about a minute later before anyone is told. DNS changes are
confirmed with the domain's own authoritative nameservers, so a change that is still spreading doesn't alert
twice. Uptime problems must be seen twice, and if many unrelated sites seem to fail at the same moment, we hold
the alert briefly in case the problem is on our side.

If a monitor can't check at all 3 times in a row, for example because a registry keeps refusing, you get one
alert saying so.

## Alerts

Alerts go to the channels you choose on each monitor; by default, an email to you. Add channels under
**Alerts**:

- **Email** to members of your account. Every alert email has a one-click unsubscribe link.
- **Webhook**: a signed JSON request to your own endpoint. [Webhooks](/docs/webhooks) describes the payload, the
  signature and how to verify the endpoint.
- **Slack**: a Slack incoming webhook URL.

Choose **Daily digest** on a channel to get warnings and information once a day at the hour you pick. Failures
are still sent at once. **Send test** sends a sample alert so you can check that a channel works.

## Check now

**Check now** on a monitor's page runs it within about a minute. It's free, up to 10 times an hour per monitor.
Lookalike monitors can be checked on demand once a day.

## Using the API

curl: create an SSL monitor

```sh
curl -X POST "https://api.dnssuper.com/v1/monitors" \
  -H "Authorization: Bearer $DNSSUPER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"ssl","target":"example.com"}'
```

`GET /v1/monitors` lists your monitors with your plan's limits, `GET /v1/monitors/{id}/events` lists a
monitor's events, and `PATCH` and `DELETE` on `/v1/monitors/{id}` change or remove one. Send the same
`X-Request-Id` again to retry a create safely: you get back the monitor it already made.
