Check authentication
Review SPF, DKIM and DMARC, including whether the DMARC policy is enforced or passive.
A DMARCian alternative that catches sender changes.
See what changed in your sending domain and get the right people on it. MailSlurp combines scheduled checks, clear findings and team alerts.
Trusted by teams at
Find the weak link in your sending domain.
A missing record, incomplete DKIM check or passive DMARC policy can be easy to overlook. MailSlurp brings the findings together so you can see what passed, what needs attention and what has not been checked.
Explore the domain checks
Inspect routing and trust
See MX and blocklist findings alongside BIMI, MTA-STS and TLS reporting checks.
Keep unknowns visible
Distinguish warnings, failures and unchecked signals before deciding what needs investigation.
Catch the change. Tell the right people.
Keep checking after the DNS setup is finished. Schedule runs, compare the findings and alert your team when a sending-domain change needs attention.
Send alerts to email, Slack, Microsoft Teams or a webhook. Choose the severity for each destination, then open the affected run to investigate the records behind it.
Set up domain monitoring
Check before an important send
Run an on-demand check after a DNS update or before a campaign.
Follow the run history
Compare findings before and after adding a sending service or changing a record.
Connect your existing workflow
Use webhooks to bring findings into the tools your operations team already uses.
See what happened to the email, too.
Pair domain monitoring with an inbox placement test through your real sending provider. Authentication findings help explain the sender; provider results show where the tested messages landed.
Test inbox placement
How to keep your sending domain in view
Add the domain and run a check
Enter the domain you send from, add the relevant DKIM selectors and inspect the first result. Keep warnings, failures and unchecked signals separate.
Set a schedule and alert destination
Choose how often to check the domain and where your team should hear about changes. Send alerts to email, Slack, Microsoft Teams or a webhook.
Investigate the changed record
Open the affected run and compare it with the previous result. After a correction, run another check and test a representative email's placement. The domain monitoring guide covers setup and findings.
Catch the configuration change before the next campaign.
Review the policy and the sending services behind it
A domain can have a DMARC record and still need attention. Use MailSlurp to inspect the policy, SPF and relevant DKIM checks together. Add the selectors used by your active sending services so an untested signature is not mistaken for a pass.
Retest after the DNS correction
Start your DMARCian comparison with a domain change your team needs to verify. Run a baseline, apply the intended DNS correction through your normal process and check the next result. Keep a schedule and alert destination in place, then test a representative email through the same sender.
Questions before you switch?
What should I investigate after the first domain check?
Start with failures, warnings and anything that was not checked. Confirm the DKIM selectors for your active sending services and inspect the DMARC policy alongside SPF and MX findings. After a DNS correction, run another check and compare the result. A representative placement test adds evidence about the actual email your sender delivers. Understand domain findings and follow-up checks.
Which records can I investigate?
MailSlurp brings SPF, DKIM, DMARC, MX, blocklist, BIMI, MTA-STS and TLS reporting findings into domain monitoring. Add the relevant DKIM selectors and review unchecked signals separately from passes.
How does my team hear about a change?
Configure alerts for email, Slack, Microsoft Teams or a webhook. Choose the minimum severity, then open the affected run to investigate the underlying finding.
Keep your sender ready for the next campaign.
Run the domain checks and bring your team into the result.
