- Checked
- 2026-11-14
Mail from your server lands in spam. Check these records.
Big mailbox providers decide on a few public facts: whether your domain says this server may send for it, whether the message is signed, what the domain wants done with failures, and whether the server's address has a matching name. All four can be read from outside in a few minutes.
Read what the receiver decided
Send a message to a Gmail or Outlook address you own and open its headers, Show original in Gmail. The Authentication-Results line gives spf=, dkim= and dmarc= with pass or fail for each. That is the receiver telling you what failed.
The four records
- SPF:
dig +short TXT example.comshows the record that startsv=spf1. It must name every server and service that sends as the domain, the web server included. A domain may publish only one SPF record, and checking it may take at most ten DNS lookups. - DKIM: the mail software signs each message with a key whose public half sits in DNS at
selector._domainkey.example.com.dig +short TXT selector._domainkey.example.comshould return it; the selector is thes=value in theDKIM-Signatureheader of a sent message. - DMARC:
dig +short TXT _dmarc.example.com. Start withv=DMARC1; p=none; rua=mailto:you@example.comto get reports with no risk to delivery, and move to quarantine once the reports show only your own senders. - Reverse DNS:
dig +short -x 203.0.113.10, with your server's address, should return a name, and that name should point back to the same address. It is set in the hosting provider's panel, not in your own DNS.
What Gmail asks of senders
Since February 2024 Google asks every sender to Gmail for SPF or DKIM, valid forward and reverse DNS and a TLS connection, and a spam rate in Postmaster Tools below 0.3 percent. Senders of more than 5,000 messages a day to Gmail also need SPF, DKIM and DMARC, a From domain aligned with SPF or DKIM, and one-click unsubscribe on marketing mail.
Mail sent by the site itself
A contact form or a shop that sends through PHP's mail() goes out from the web server with no DKIM signature, often from an address the SPF record does not list. Send it over SMTP through the domain's real mail service, with a login, and it gets that service's SPF and DKIM.
If the server's address is on a blocklist, mail sent from it directly keeps landing in spam until it is delisted. A server that suddenly sends a lot of mail you did not write has usually been broken into. The free email check reads a domain's MX, SPF, DMARC and DKIM records in one go.
What not to do
- Do not add a second SPF record for a new service. Add the service to the one record you have.
- Do not start DMARC at
p=reject. A sender you forgot, an invoicing tool for example, then has all its mail refused. - Do not ask recipients to mark you as safe and call it fixed. It helps one inbox and hides the cause from all the others.
When to stop and hand it over
Stop if the records look right and mail still fails, if the server's address is blocklisted, or if the server may have been used to send spam. Our Server Rescue is one incident at a fixed $69, with a same-day start listed at $109, and nothing to pay if we cannot fix it.
Questions people ask
- Why does my mail go to spam even with SPF?
- For many receivers SPF alone is no longer enough. Without DKIM and DMARC, or with a From address that does not match the domain that passed, the message still looks suspicious.
- What is a safe first DMARC record?
v=DMARC1; p=none; rua=mailto:followed by an address you read. It changes nothing for delivery and sends you reports on who sends as your domain.- Can I fix this without access to the mail server?
- The DNS records, yes, wherever the domain's DNS is managed. DKIM keys need the mail service, and reverse DNS needs the hosting provider.
- What does fixing it cost?
- With us, Server Rescue at $69 for the incident, or $109 for a same-day start. If we cannot fix it, you pay nothing.
Where each statement comes from
Checked against the sources on .
- Google: email sender guidelines (support.google.com)
- RFC 7208: SPF (rfc-editor.org)
- RFC 6376: DKIM signatures (rfc-editor.org)
- RFC 7489: DMARC (rfc-editor.org)
More server help
- DNS not resolving or still on the old server
- Website hacked: the first steps
- WordPress white screen or critical error
- Linux server hardening checklist
- Server down: what to check first
- 502 Bad Gateway on nginx
- 504 Gateway Timeout
- Error establishing a database connection
- Too many redirects
- 403 Forbidden on nginx or Apache
- Disk full: no space left on device
- SSL certificate expired: the fix
- Renewing a Let's Encrypt certificate
- Moving a site to a new server
- All server help guides
