
You can write the perfect email and still never be read if it lands in spam or is rejected outright. Deliverability is the discipline of making sure legitimate mail reaches the inbox. For anyone sending from a custom domain, including contact-form notifications and automated replies, three DNS records are the foundation: SPF, DKIM and DMARC.
Why this matters
Email was designed without strong sender verification, so anyone can claim to send from your domain. Mailbox providers such as Gmail, Outlook and Yahoo therefore check whether a message is really authorised. Since 2024, Google and Yahoo have required authentication for bulk senders, and unauthenticated mail from small senders is increasingly filtered too.
SPF: who may send for this domain
SPF (Sender Policy Framework) is a DNS TXT record listing the servers allowed to send mail for your domain. The receiving server compares the connecting server’s address with that list.
- You have only one SPF record per domain. Combine all services into a single record, for example your mail host and your newsletter tool.
- The record ends with a policy:
~all(soft fail) or-all(hard fail). - SPF allows at most ten DNS lookups; too many “include” entries make it fail.
DKIM: a signature that proves the message was not altered
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message. You publish the public key in DNS, and receivers use it to verify that the message came from your domain and was not changed in transit. Your mail provider generates the key pair and gives you the record to publish. Enable it for every service that sends on your behalf.
DMARC: what to do when checks fail
DMARC ties the two together. It tells receivers that SPF or DKIM must pass and align with the visible From domain, and what to do otherwise: nothing (p=none), quarantine, or reject. It also asks them to send you reports.
- Start with
p=noneand a reporting address, to see who sends mail as your domain. - Fix any legitimate senders that fail.
- Move to
quarantine, thenreject, once everything legitimate passes.
Other factors that affect inbox placement
- Reputation. A new domain or IP has none; increase volume gradually.
- Content. Avoid spammy phrasing, deceptive subject lines, and messages that are only one large image.
- Engagement. Messages that people open and reply to build reputation; those that are ignored or reported hurt it.
- Clean lists. Remove addresses that bounce, and honour unsubscribes quickly.
- Consistent sending identity. Use the same From name and a real address that can receive replies.
- Reverse DNS and TLS. Your sending server should present a valid hostname and use encryption. Managed providers handle this for you.
How to test your setup
- Send a message to a Gmail account, open “Show original” and look for
SPF: PASS,DKIM: PASSandDMARC: PASS. - Use a free checker such as Google Admin Toolbox’s Check MX, MXToolbox, or mail-tester.com for a score and specific advice.
- Look up your records with
dig TXT yourdomain.comto confirm only one SPF record exists.
For automated emails
Notifications from forms and workflows are easy to forget. Send them through a proper mail service or your domain’s authenticated SMTP rather than a generic server, make sure the From address belongs to a domain you have authenticated, and monitor bounce messages.
Key takeaways
Publish SPF, DKIM and DMARC for every domain that sends email, begin DMARC in monitoring mode, send relevant mail to people who want it, and test after each change. These steps are free and make the single biggest difference to whether your messages are seen.