Guides ·
Why is my email going to spam?
Most often, the servers receiving your email fail to confirm it really came from you. Two short DNS records – SPF and DMARC – are how your domain proves it, and the check below reads both from public DNS.
How a receiving server decides
Gmail, Outlook and other providers ask three questions of every message: is the sending server allowed to send for this domain (SPF), is the message signed by the domain (DKIM), and what does the domain want done with mail that fails (DMARC). Since February 2024, Google and Yahoo require all three from anyone sending in bulk.
SPF: which servers may send for you
SPF is one TXT record listing the services allowed to send your email – your mailbox provider, your newsletter tool. A domain must have exactly one: two SPF records count as an error, and the protection stops working.
DMARC: what happens to forged email
DMARC tells receivers what to do with mail that claims to be from you but fails the checks. p=none only reports; p=quarantine sends it to spam; p=reject refuses it. Without DMARC, anyone can send email that looks like it came from your domain, and that abuse can drag down how your own email is treated.
What this check does not cover
DKIM keys live under a name only your provider knows, so no outside check can find them without it. Your sending reputation, blocklists and the content of the message also matter. If SPF and DMARC are both in place and mail still lands in spam, start with your provider's DKIM setup.