Is your domain ready for bulk email?
Enter your domain to see how Gmail, Outlook and Yahoo see it. We check your public SPF, DKIM and DMARC records and tell you, in plain language, what’s missing.
If this is the domain your team uses for everyday email, we recommend not sending campaigns from it at all — even with perfect records. A campaign that draws complaints can affect the delivery of your quotes, invoices and replies.
Don't fix your main domain for bulk email. Send from a separate one — set up for you.
Postfaro creates a separate, fully authenticated sending domain for your campaigns — SPF, DKIM and DMARC done right and locked, warm-up and bounce handling included. Your main domain stays exactly as it is.
Fix it for $20 setupSetup $20 one-time + plan $99/year · or $119/year including a new domain
What do SPF, DKIM and DMARC mean?
- SPF (Sender Policy Framework) is a DNS record that lists the servers allowed to send email for your domain. Receiving servers check whether a message came from one of them.
- DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message. The receiving server checks it against a public key in your DNS, proving the message really came from your domain and wasn’t changed on the way.
- DMARC (Domain-based Message Authentication, Reporting and Conformance) ties the two together. It tells receivers what to do with messages that fail SPF and DKIM alignment — deliver, quarantine or reject — and where to send reports.
Why does this matter now?
Since 2024, Gmail and Yahoo require bulk senders to authenticate with SPF and DKIM, publish DMARC, offer one-click unsubscribe and keep spam complaints low. Microsoft introduced similar rules for Outlook.com in 2025. Email that doesn’t meet them is increasingly filtered or rejected.
What does this checker not do?
It only reads public DNS records. It doesn’t send test emails, check blocklists or see your sending history, and it can’t predict exactly where a specific email will land. DKIM can’t be checked fully from outside without knowing the selector: we try common selector names, so a “not found” result may just mean your provider uses a custom one.
We look up only public DNS information for the domain you enter. We keep a short log of checked domains and IP addresses to prevent abuse of the tool. See our Privacy Policy.