Delete Monitoring Checks

Not every domain should stay monitored forever.

Brands merge, environments are retired, and sending infrastructure changes. But when old monitors stay around, they create dashboard noise and distract teams from real risk.

helps keep your monitoring inventory clean and trustworthy.

Domain monitor list in MailSlurp showing last status and next run time

Consider pausing before deleting

If a domain might come back, or you're in a migration window, deleting is not always the best move.

Two safer alternatives:

  • pause scheduling (keep the monitor and history, stop background runs)
  • increase interval (reduce noise without removing visibility)

Delete is best when you're confident the domain is permanently out of scope.

A practical rule of thumb

Delete a monitor when the domain is:

  • no longer used for sending
  • permanently migrated to another ownership context
  • intentionally decommissioned

Keep it when the domain still has operational relevance, even if low-volume.

Endpoint

cURL example

Successful deletion returns .

Team process that prevents mistakes

  1. Confirm domain lifecycle status with owner.
  2. Export any historical data needed for compliance/reporting.
  3. Delete monitor.
  4. Verify the monitor disappears from list and detail views.

Prune with intent

Monitoring quality is not just about adding checks. It's also about pruning stale checks so people trust what they see.