Check authentication
Review SPF, DKIM and DMARC, including whether the DMARC policy is enforced or passive.
A DMARCLY alternative for the domains you send from.
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.
Keep new sending services from becoming blind spots.
Check the domain after adding an ESP
A new email platform can introduce a new SPF include or DKIM selector. As you evaluate a DMARCLY alternative, use MailSlurp to inspect a domain before and after the change. Review authentication and MX findings, including records that still need investigation.
Give each finding a practical next step
Keep the person who manages DNS connected to the result. Configure alerts at the severity your team needs, compare successive runs and repeat the check after a correction. Use inbox placement testing to see where the new sending path puts a real campaign.
Questions before you switch?
What should I check when adding a new email provider?
Confirm the provider domain setup, the SPF record it needs and the DKIM selectors it uses. Run MailSlurp domain monitoring before and after the change and inspect the individual findings. Keep the previous result for comparison, then send a representative campaign through the new path for a separate placement check. Check records after a provider change.
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.
