Reference
Email authentication
What SPF, DKIM, and DMARC do, why your mail needs them, and what a failed check tells you.
Email authentication is a set of three checks that prove a message really came from the domain it claims. Without them, anyone can send mail that appears to be from your address.
MailMoose sets all three up when you connect a domain, and shows you the result on every message you receive.
The three checks
- SPF lists which services are allowed to send mail as your domain. A receiver looks up your SPF record and checks whether the sending server is on the list.
- DKIM adds a cryptographic signature to every message you send. A receiver verifies it against a key published in your DNS, which proves the message came from you and was not altered on the way.
- DMARC ties the two together and tells receivers what to do when a message fails. It also lets you ask for reports about mail sent in your name.
Why they matter
- Your mail reaches inboxes. Providers treat unauthenticated mail as suspicious. Gmail and Outlook now require authentication for most senders.
- Nobody can impersonate you. Without DMARC, a scammer can send invoices that appear to come from your domain, to your own customers.
- You can see when others are impersonated. Every message you receive shows whether it passed.
Reading the badge on a message
Each message in your inbox shows the outcome of these checks.
| Badge | Meaning |
|---|---|
| Verified | The message passed. The sender is who they claim to be. |
| Failed DKIM, SPF, or DMARC | Something did not check out. Treat the message with suspicion. |
A failed check does not always mean fraud. Forwarded mail sometimes breaks SPF legitimately. But an unexpected invoice from a supplier that fails DMARC deserves a phone call before you pay anything.
Tightening DMARC over time
MailMoose starts your DMARC policy permissive, which means receivers are told to accept mail that fails and simply report it. That is deliberate. A strict policy on a new domain can silently send your own mail to spam while records settle.
Once you have run for a few weeks without problems, you can tighten the policy at your registrar:
p=nonereports failures but delivers everything. This is where you start.p=quarantinesends failing mail to spam.p=rejectrefuses failing mail outright. This is the strongest setting.
Move one step at a time and watch for problems before going further.
Related
Last updated 2026-08-20