# Domain Monitor

Domain Monitor helps teams keep sender configuration healthy over time. It is designed for the operational reality that domains change, DNS records drift, and a working sender setup can quietly become risky if nobody is watching it.

## What Domain Monitor is for

Use Domain Monitor when you need to keep track of:

- SPF records
- DKIM alignment and key configuration
- DMARC policy posture
- MX and related delivery dependencies
- sender-domain changes that could affect launch readiness or ongoing deliverability

## Who typically uses it

- platform teams responsible for production email infrastructure
- lifecycle teams that depend on branded sender domains
- release teams that want to verify sender posture before large sends

## Recommended workflow

1. Add the domain or domains you care about.
2. Confirm the expected authentication and routing posture.
3. Review status before major campaigns or releases.
4. Re-check whenever DNS, mail infrastructure, or ownership changes.

## What to do when a domain needs attention

Start with the item that changed or failed, then work outward:

1. confirm which DNS record or sender-health signal changed
2. compare it to the expected production setup
3. correct the configuration in DNS or the sending platform
4. re-run the review before resuming large sends

## How it fits with other docs

- Use [Custom domains](/docs/custom-domains/) when you are setting sender identity up for the first time.
- Use [Campaign Probe](/docs/campaign-probe/) when you need to review actual live campaign output.
- Use [Deliverability tests](/docs/deliverability-test/) when you need a pass/fail release or launch check.
- Use [Reputation](/docs/reputation/) when sender-health risks show up in delivery outcomes.