Per-check controls

Per-check controls let you tune how DomainCare runs checks and fires notifications on a domain-by-domain, check-by-check basis. You can stop a check from running entirely, silence its alerts, change how often it runs, mute or override the severity of individual event types — and reset everything back to defaults in one click.

Per-check controls are available on paid plans.

Where to find them

Two surfaces, same data:

• Bulk view at Settings → Notifications on the per-domain settings page (/domains/<id>/settings). One row per check, with quick Stop / Mute / Reset buttons and the per-event toggles.
• Per-check page at /domains/<id>/checks/<type> → Settings tab. Adds the interval picker and the per-event severity overrides.

Both surfaces write to the same domain_check_override row.

Stop vs. Mute

Two related but distinct knobs:

• Stop halts scheduling. The check is removed from the cron pass — it doesn't run, no new results land, no events fire. The check's other settings (interval override, mute, per-event toggles) are preserved; starting it again resumes from where you left off.
• Mute keeps the check running. Results still land in history and feed health calculations, but no notifications fire — neither immediate alerts nor digest entries.

Use Stop for staging domains where you don't want to spend cron time on the check at all. Use Mute when you still want history but don't want pages.

Interval override

Every check runs on a default cadence. You can override the cadence per domain using class-tiered presets — no free-form seconds input.

Presets are grouped by the check's default interval:

Class	Applies to	Available presets
Fast	Uptime, SSL (≤10 min default)	1 min / 5 min / 15 min
Medium	DNS, email auth, robots.txt (≤2 h default)	15 min / 1 h / 6 h
Slow	RDAP, redirect, sitemap, nameservers, Lighthouse, blacklist (>2 h default)	6 h / 24 h / 7 days

Select a preset and save. The scheduler reads the override on the next scheduled run and applies it from that point forward. Setting the override back to Default restores the registry default.

The default uptime interval is 1 minute on all plans. The slowest uptime preset (15 min) checks less frequently — useful for staging domains where you don't need real-time uptime data.

Per-event-type mute

Within a check, you can disable individual event types while keeping others active. For example, you might want to receive ssl_cert_expired alerts but not ssl_weak_cipher_detected warnings until you can rotate the cipher configuration.

Each event type has a toggle. Disabled event types are recorded in disabled_event_types on the check override row. Events of that type still appear in history but never dispatch an alert.

Failure ↔ recovery toggles move together. Silencing mx_records_missing automatically silences mx_recovered (and vice versa). Otherwise you'd hear the recovery alert for an outage you never heard about. The same pairing applies to website_down ↔ website_back_online, ssl_validation_issue ↔ ssl_recovered, and every other failure-with-a-paired-recovery event. Failures without a 1:1 recovery (like ssl_weak_cipher_detected) toggle on their own.

Example use cases:

• Silence ssl_weak_protocol_detected on a legacy internal tool while keeping cert-expiry alerts.
• Disable robots_content_changed on a CMS domain where robots.txt changes frequently.
• Mute dns_ttl_dropped_low during a planned DNS migration to avoid noise.

Severity override

Event severities are set by DomainCare based on the type of change detected. You can override the effective severity per event type on a per-domain basis — for example, treating dmarc_policy_changed as Critical on your primary sending domain.

Severity overrides apply at event insert time, so the override affects everything downstream consistently — the severity stamp shown in the activity log, the digest tier filter, the channel routing, and the email tone all read from the same persisted value. Change an override and it applies to events fired after the change, never retroactively.

Reset to defaults

Once you've configured overrides on a check, a Reset button appears. It deletes the override row entirely — wiping the interval override, the mute flag, the stop flag, every per-event toggle, and every severity override in a single action. The check returns to registry defaults.

Reset is available both as a per-row button on the bulk view and as a footer on the per-check Settings tab. Both render only when at least one override is active, so the button never confuses users on a check at defaults.

Recovery event routing

Most recovery events (ssl_recovered, mx_recovered, dmarc_recovered, etc.) are assigned Low severity by default. Low-severity events are routed to the weekly/daily digest rather than firing an immediate alert. This means you may receive a Critical ssl_cert_expired alert immediately, but the matching ssl_recovered event lands in your next digest instead of arriving as an instant notification.

Exceptions:

• website_back_online — assigned Critical severity; fires immediately so you know the outage is over.
• blacklist_delisted — assigned Needs-attention severity; fires immediately.

If you want immediate delivery for a specific recovery event, use the severity override control on the check's settings page to promote it to Critical or Needs-attention.

How suppression is logged

Every skipped notification is recorded in the suppression log with a reason:

Reason	Meaning
check_muted	Mute is on for this check on this domain
event_type_disabled	This specific event type is in the disabled list
severity_gate	Effective severity is low or info — goes to digest only
maintenance_window	Domain is inside a maintenance window
quiet_hours	Medium event arrived during quiet hours
no_matching_rules	No enabled notification rule matches this event
rate_limited	Org outbound rate limit reached
debounce	Failure event suppressed pending 2-fail confirmation

View the suppression log at Settings → Notifications → Delivery log.

Common questions

Do per-check controls affect the digest? Muted checks and disabled event types suppress both immediate and digest delivery. If you want digest-only delivery, use severity settings on your notification rules rather than per-event-type mutes.

Can I copy per-check settings from one domain to another? Not yet — each override is set per-domain via the UI. Bulk copy is deferred.

What happens to overrides if I delete a domain? Override rows are deleted with the domain row in a cascade.

---