Check authentication
Review SPF, DKIM and DMARC, including whether the DMARC policy is enforced or passive.
An MXToolbox alternative that watches between checks.
Monitor your sending domain, inspect changed records and alert your team. MailSlurp connects domain checks with the email your customers receive.
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.
Turn a one-off investigation into an ongoing check.
Check the domain behind your email
An MX lookup helps during an incident. A scheduled domain monitor keeps checking after that incident is closed. Use MailSlurp to review authentication, routing and blocklist findings in one run history.
Alert the team when a record changes
Begin with the sender domain behind your campaign, add the DKIM selectors you use and choose alert destinations. When a result changes, open the affected run, investigate the specific record and run a placement test through the same sending service.
Questions before you switch?
How do I turn a one-off DNS lookup into ongoing monitoring?
Add the sending domain to MailSlurp, run a baseline and configure the relevant DKIM selectors. Set the check frequency and alert destinations, then compare later findings with the original run. After a DNS correction, run another check and use a representative placement test to inspect the sending path as well. Set up recurring domain checks.
Can I monitor email blacklists and authentication together?
Yes. 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.
