Domain expiry monitors
The registration of a domain, looked up through DomainRadar at most hourly. Alerts before it expires, when it expires, and when it is not registered at all.
A domain monitor watches a domain's registration: when it expires, who the registrar is, and whether it is registered at all. The lookup goes through DomainRadar, which owns the RDAP and WHOIS access, the proxies, the rate limits and the cache. Norcube Monitor never asks a registry itself.
Settings
| Field | Rules | Dashboard default |
|---|---|---|
| Domain | The registered domain: example.com, not www.example.com. At most 253 characters. Internationalized names may be typed in Unicode; they are stored in punycode. | required |
| Warn before expiry (days) | Up to 5 thresholds of 1 to 365 days. Empty alerts only once the domain has expired. | 30, 14, 7 |
Domain monitors are checked at most hourly, whatever your organization's limit allows for other kinds. New ones start at 12 hours in the dashboard and the CLI.
What a check finds
| Condition | Severity | Word | Incident |
|---|---|---|---|
ok | ok | Registered | |
domain_expiring | warning | Expiring | At once, and again at each threshold |
domain_expiry_unknown | warning (quiet) | Expiry unknown | Never |
domain_expired | critical | Expired | At once |
domain_not_registered | critical | Not registered | At once |
domain_lookup_failed, internal | inconclusive | Unknown | Never |
Expiry unknown means the domain resolves and is registered, but the registry publishes no expiry date, so the monitor can't warn ahead. It shows as a warning in the list so you know, but it opens no incident and sends no alert: there is nothing you can change. A failed lookup is inconclusive: the status, the incident and the history stay as they were, and the page says since when it couldn't verify.
The expiry date is the registry's calendar date at 00:00 UTC. The days remaining are 0 on the expiry day and negative after it.
The monitor page
The hero shows the days until the registration expires, with your
thresholds on a timeline and the alerts already sent. Registration
details shows what the newest lookup returned: the domain, the
registrar, the source (RDAP, WHOIS, or DNS only when the registry
wasn't asked and there are no dates), when it was looked up, the
registration and last-update dates, DNSSEC (signed or not), the
nameservers and the EPP status codes (clientTransferProhibited,
pendingDelete, ...), each explained on hover. What the registry
doesn't publish is left out.
Monitors managed by DomainRadar
When you turn expiry alerts on for a saved domain in DomainRadar, it creates a domain monitor here and links it. Such a monitor shows Managed by DomainRadar. You can rename it and change its interval and thresholds in Norcube Monitor; its domain is set in DomainRadar, and turning the expiry alerts off there removes it. Deleting it here is refused.
Create one from the CLI
nrc monitor monitors create "example.com" --type domain --domain example.com --interval 24hEvery flag is in the CLI reference.
SSL certificate monitors
A TLS handshake to a host and port on every check. Chain, hostname and validity are verified, expiry alerts fire at your thresholds, and the certificate's details and renewals are kept.
Alerts
Alert channels (email, webhook, Slack, Discord, SMS), verification, default channels, routes per monitor and event, confirmation and reminders, test sends, and the delivery log with retries.