
Check authentication
Review SPF, DKIM and DMARC, including whether the DMARC policy is enforced or passive.
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



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

Review SPF, DKIM and DMARC, including whether the DMARC policy is enforced or passive.

See MX and blocklist findings alongside BIMI, MTA-STS and TLS reporting checks.

Distinguish warnings, failures and unchecked signals before deciding what needs investigation.
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

Run an on-demand check after a DNS update or before a campaign.

Compare findings before and after adding a sending service or changing a record.

Use webhooks to bring findings into the tools your operations team already uses.
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
Enter the domain you send from, add the relevant DKIM selectors and inspect the first result. Keep warnings, failures and unchecked signals separate.
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.
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.
Choose MailSlurp when domain checks need to connect with everyday campaign operations. A marketer can see that a sender needs attention, while the person managing DNS can open the same run and inspect the record finding. Configure email, Slack, Teams or webhook destinations around those responsibilities.
Use one domain to evaluate the switch from EasyDMARC. Review its initial results, choose a monitoring schedule and check your alert settings. After a planned DNS change, inspect the next run and confirm the relevant teammate can find the details without reconstructing the issue from screenshots.
Choose email, Slack, Microsoft Teams or a webhook as the alert destination and set the severity relevant to that audience. Run a baseline check and make sure the team knows how to open the affected result. When a finding changes, inspect the record and compare runs before deciding which sending service or DNS setting needs attention. Configure domain schedules and notifications.
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.
Domain checks help you investigate authentication and configuration. Test the finished campaign separately through its normal sending provider to see where the tested copies arrive. MailSlurp keeps inbox, Promotions, spam and missing results distinct so your team can investigate the provider that needs attention. Test the campaign's inbox placement.
Run the domain checks and bring your team into the result.
