Find where your website's email delivery is going wrong
A password reset in the spam folder can leave someone waiting for a message that's already arrived. Authentication is a useful place to start, but it's only part of the investigation.
How do I find out why emails go to spam?
- 1
Check authentication first
Review 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.
- 2
Confirm the domain your sending service uses
Compare 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.
- 3
Review reputation and complaints
Read your sending provider's delivery records and the receiver's sender tools. Look for spam complaints and shared-IP problems.
- 4
Examine the message and its links
Check 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.
Keep account messages separate from marketing
Yahoo recommends separating transactional mail from bulk marketing by sending IP or DKIM domain. Review whether a newsletter and your app's password emails share the same sending setup before changing only the app's DNS.
Yahoo's sender recommendations explain how sending practices affect reputation.
What if only one email provider sends my mail to spam?
Gmail's Postmaster Tools can show sending reputation and spam complaints. For Outlook.com, Hotmail and Live recipients, check your sending service's rejection details and Microsoft's sender support guidance. If the problem affects one receiver, look for evidence from that receiver.
Frequently asked questions
Should I keep changing DNS if authentication already passes?
First confirm the result on mail sent by the affected service. If it passes and aligns with your From domain, continue with provider setup, complaints and the message itself rather than making an unrelated DNS change.
What if the message was rejected instead of sent to spam?
Read the rejection code in your sending provider's delivery record. It may name an authentication or sender-policy problem. That gives you a different starting point than a message accepted into a spam folder.
Investigate records and receiver requirements
SPF, DKIM and DMARC
Find out why your emails land in spam, and who else can send mail as you.
SPF record
Lists the servers allowed to send your domain's mail.
DKIM record
Lets receivers check each message's signature against a key your domain publishes.
DMARC record
Tells receivers what to do with mail that fails, and where to send reports.
Gmail, Yahoo and Outlook sender requirements
Compare provider requirements and see which a record check covers and which depend on how you send.