Fix SPF, DKIM and DMARC so your emails land in the inbox, not spam
If your emails land in spam, or someone sends mail pretending to be you, the cause is often three records in your domain's DNS. They tell receiving mail servers which servers may send your mail, how to check it really came from you, and what to do when it didn't.
yoursite.com. TXT "v=spf1 include:mail.example.net +all"Your SPF email sender record has a problemselector1._domainkey.yoursite.com. no recordNo DKIM email signature record found_dmarc.yoursite.com. TXT "v=DMARC1; p=none"DMARC email record is missing, weak or brokenThis free check reads your domain's SPF, DKIM and DMARC records, the same public records mail servers read. It shows what passed, what failed and why it matters.
What a scan can flag, and what it can't promise
A scan can flag
- Your SPF, DKIM and DMARC recordsThe same public records receiving mail servers read.
- What passed and what failedWith why each result matters for your mail.
What it can't promise
- A place in the inboxReceivers also weigh things like spam complaints, and a DMARC pass doesn't guarantee the inbox.
- A DKIM selector it didn't tryCheck a message you sent, or your provider's settings, for the selector your mail uses.
Explore your email setup
Prove your emails really come from you
4 guides
Lists the servers allowed to send your domain's mail.
How to fix
- In your DNS settings, where your domain's records live, usually at your domain registrar or DNS host, add one TXT record, a plain text record, for your main domain, often entered as @, that starts with v=spf1.
- In that record, list each service that sends email as you, like your email provider or newsletter tool, using the include value it gives you, such as include:_spf.google.com for Google, and end it with ~all or -all, never +all.
- If your domain never sends email, make the record just v=spf1 -all, and never add a second v=spf1 record.
- Then run the check again.
Your SPF email sender record has a problem
Your domain's list of allowed email senders is missing or has a problem, which may let fake mail through or block real mail.
Fix with your agent
# SiteCMD Fix Brief: Your SPF email sender record has a problem Site: https://yoursite.com ## What is wrong Your domain's list of allowed email senders is missing or has a problem, which may let fake mail through or block real mail. ## How to fix Publish exactly one TXT record at the apex starting with `v=spf1`, naming every service that sends mail for the domain (for example `include:_spf.google.com`), and end with `-all` or `~all`, never `+all`. Keep the record under 10 DNS-querying terms, never add a second `v=spf1` record, and if the domain never sends mail, publish `v=spf1 -all`. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Lets receivers check each message's signature against a key your domain publishes.
How to fix
- Open the full message headersUse a message sent by the service you want to investigate. Find its DKIM-Signature header, rather than the sender name shown above the message.
- Read the selector and signing domainThe s= value names the selector. The d= value names the signing domain. Together they identify the key's DNS name.
No DKIM email signature record found
Your outgoing mail is not being signed, so recipients have no way to confirm it truly came from your domain unaltered.
Fix with your agent
# SiteCMD Fix Brief: No DKIM email signature record found Site: https://yoursite.com ## What is wrong Your outgoing mail is not being signed, so recipients have no way to confirm it truly came from your domain unaltered. ## How to fix Enable DKIM signing in each provider that actually sends your mail (it is a provider setting, not something you invent yourself), then publish the CNAME or TXT record it gives you at `<selector>._domainkey.yourdomain.com`. Validate a real delivered message afterward; DNS key publication alone does not prove outbound mail is signed or that its signing domain aligns for DMARC. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Tells receivers what to do with mail that fails, and where to send reports.
How to fix
- In your DNS settings, add a TXT record, a plain text record, named _dmarc that starts in watch-only mode, for example v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com, using an address where you can receive reports.
- For a couple of weeks, read the reports to find any of your real email services whose mail fails, and fix how that service is set up to send for your domain.
- Once the reports stay clean, change p=none to p=quarantine, and later to p=reject.
- Then run the check again.
DMARC email record is missing, weak or broken
Your domain's rule for handling mail that cannot prove it came from you is missing, only watches, or does not work.
Fix with your agent
# SiteCMD Fix Brief: DMARC email record is missing, weak or broken Site: https://yoursite.com ## What is wrong Your domain's rule for handling mail that cannot prove it came from you is missing, only watches, or does not work. ## How to fix Publish a TXT record at `_dmarc.yourdomain.com` starting in monitoring mode, for example `v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com`, then review the aggregate reports for a couple of weeks to find legitimate senders that fail SPF or DKIM alignment. Fix any legitimate sender that fails alignment, then graduate to `p=quarantine` (optionally ramping with `pct`) and finally `p=reject` once reports stay clean. Rejection reduces exact-domain spoofing; it does not stop display-name impersonation or lookalike domains. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Understand the consequences before tightening how receivers treat failing mail.
How to fix
- Identify the services that send as your domainInclude the app's sign-up and password messages, support systems and any mailing service. Check each sender's authentication and alignment before changing the policy.
- Review failures while the policy is noneUse receiver reports and your sending service's delivery records to tell forgotten senders apart from unauthorized mail. Fix failures affecting legitimate mail before asking receivers to enforce the policy.
- Move to quarantine when the evidence supports itWatch for legitimate messages being treated as suspicious. Check the effects of forwarding and mailing lists rather than assuming every failure is forgery.
- Consider reject after resolving the remaining failuresCheck delivery results again after the change. Keep the previous policy handy in case legitimate mail starts failing.
DMARC email record is missing, weak or broken
Your domain's rule for handling mail that cannot prove it came from you is missing, only watches, or does not work.
Fix with your agent
# SiteCMD Fix Brief: DMARC email record is missing, weak or broken Site: https://yoursite.com ## What is wrong Your domain's rule for handling mail that cannot prove it came from you is missing, only watches, or does not work. ## How to fix Publish a TXT record at `_dmarc.yourdomain.com` starting in monitoring mode, for example `v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com`, then review the aggregate reports for a couple of weeks to find legitimate senders that fail SPF or DKIM alignment. Fix any legitimate sender that fails alignment, then graduate to `p=quarantine` (optionally ramping with `pct`) and finally `p=reject` once reports stay clean. Rejection reduces exact-domain spoofing; it does not stop display-name impersonation or lookalike domains. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Keep your emails out of spam
2 guides
Work through authentication, sender setup and the signals a DNS scan can't see.
How to fix
- Check authentication firstReview SPF, DKIM and DMARC, then inspect a received message's authentication results. The records in DNS tell you about the setup; a message's results tell you how that message was checked.
- Confirm the domain your sending service usesCompare the visible From domain with the domains used for SPF and DKIM. Review the service's setup for your own domain, including the app's actual sending configuration.
- Review reputation and complaintsRead your sending provider's delivery records and the receiver's sender tools. Look for spam complaints and shared-IP problems.
- Examine the message and its linksCheck that the subject, sender identity and links match what the recipient requested. Look for unexpected promotional content in messages people need for an account action.
Compare provider requirements and see which a record check covers and which depend on how you send.
Read the guide: Gmail, Yahoo and Outlook sender requirementsFrequently asked questions
Do I need SPF, DKIM and DMARC if my site only sends sign-up and password emails?
Yes, if any of it goes to Gmail or Yahoo addresses. Both require every sender to set up SPF or DKIM, and larger senders to add DMARC. DMARC lets you ask receivers to refuse mail forged in your name.
Why does the check say no DKIM key was found when my mail is signed?
Your mail provider may use a selector name the check didn't try. Each message's signature names its selector. Check a message you sent or your provider's settings to find the one your mail uses.
Will fixing these records keep my mail out of spam?
Not on their own. They prove your mail really comes from you, which Gmail and Yahoo require of every sender. Receivers also weigh things like spam complaints, and the DMARC standard says a pass doesn't guarantee the inbox.
Does the check send email or need access to my DNS?
No. It reads public DNS records and your home page as any visitor sees it. It doesn't send mail or need a login.