SPF: who may send for your domain
SPF (Sender Policy Framework) is a TXT record on your domain that lists the servers allowed to send mail for it. When a message arrives, the receiving server checks whether the sending server is on that list.
A typical record names your providers and ends with a rule for everyone else. Be aware that SPF allows at most ten DNS lookups, and each include counts toward that limit, so stacking many sending services can break it.
v=spf1 include:_spf.google.com include:mail.example-sender.com ~allDKIM: proof the message was not altered
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message. Your sending service signs with a private key, and you publish the matching public key in DNS at a name made from a selector, such as selector1._domainkey.example.com.
The receiving server fetches that public key and checks the signature. If it matches, the message was sent by someone holding the key and was not changed in transit. Each service you send through usually gives you its own selector and record.
DMARC: what to do when checks fail
DMARC ties the two together. It is a TXT record at _dmarc.yourdomain that tells receivers what to do when a message fails SPF and DKIM alignment, and where to send reports about it. Alignment means the domain that passed SPF or DKIM must match the domain in the visible From address.
The policy has three levels. p=none only monitors and sends you reports. p=quarantine asks receivers to treat failures as suspicious, usually by sending them to spam. p=reject asks them to refuse the message outright.
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; adkim=s; aspf=sA safe rollout order
Start with SPF and DKIM for every service that sends as your domain, including your newsletter tool, CRM and transactional provider. Then publish DMARC with p=none and read the reports for a few weeks to find senders you forgot. Once legitimate mail passes consistently, move to quarantine, then reject.
Going straight to reject is the common mistake. A forgotten sender, such as an invoicing tool, will then have its mail refused with no warning.
- Inventory every service that sends as your domain.
- Publish SPF and enable DKIM signing in each service.
- Publish DMARC with p=none and a reporting address.
- Tighten the policy only after reports look clean.
Authentication and list quality work together
Authentication tells providers that you are who you say you are. List quality tells them that you send to people who want your mail. You need both: a perfectly authenticated sender that bounces constantly still gets filtered. Check your records with the free SPF, DKIM and DMARC checkers, and verify your list before big sends.
Authentication proves identity. A clean list proves good behaviour. Providers look at both.
Key takeaways
0/4Try it on a real address
Run syntax, DNS, MX, disposable, and role checks on any address. No signup needed.
Enter an address and press Check.
Runs real syntax, DNS and mail-server checks.
This demo checks syntax, domain, mail server, disposable and role-address rules. Sign up free for live mailbox checks.
Frequently asked questions
Verify addresses with one API call.
250 free checks to start, no card required. Unknown results are never billed.