Verify sending domains with DKIM, SPF and staged DMARC
Add a domain and Minket lists the records to publish, checks them, and shows what fails and why.
Add a domain and Minket lists the records to publish, checks them, and shows what fails and why.
Domains
mail.fernbank.example
Live mail waits until the SPF record on the bounce host checks out.
CNAME7f3a9c._domainkey.mail.fernbank.example7f3a9c.dkim.amazonses.comVerifiedCNAMEb21e04._domainkey.mail.fernbank.exampleb21e04.dkim.amazonses.comVerifiedCNAMEc9d811._domainkey.mail.fernbank.examplec9d811.dkim.amazonses.comVerifiedMXbounce.mail.fernbank.example10 feedback-smtp.<region>.amazonses.comVerifiedTXTbounce.mail.fernbank.examplev=spf1 include:amazonses.com ~allThe TXT on the bounce host does not include amazonses.com.FailedTXT_dmarc.mail.fernbank.examplev=DMARC1; p=none; rua=mailto:dmarc@fernbank.exampleVerifiedThen every 6 hours, and test keys keep working while a record fails.
403 domain_authentication_failed SPF, DKIM or DMARC is failing for this domain. Sending resumes when DNS is fixed.
It tightens one step at a time, and only while the domain passes.
p=noneReceivers report; nothing is filtered.p=quarantineMail that fails goes to spam.p=rejectMail that fails is refused.With a Cloudflare token the console lists what it would write, writes it, and never changes a record it did not create.
| Record | Type | Plan |
|---|---|---|
| DKIM | 3 CNAME | create |
| MAIL FROM | MX | create |
| SPF | TXT | create |
| DMARC | TXT | already in place |
Reports sent to dmarc@ become the domain's 30-day pass rate.
Gmail's view of the domain, once it sends a few hundred messages a day to Gmail.
Inbox placement checked every 7 days across up to 10 seed inboxes.
Your logo in the inboxes that show one, from p=quarantine up.
Yes: mail.fernbank.example gets its own records and checks, apart from fernbank.example.
No. Publish the records at any DNS host; the token only saves the copying.
Up to 50.