Why These Records Exist
Email was designed at a time when nobody expected people to lie about who they were, so the From address on a message is just text anyone can type.
These records were added later to give the receiving server a way to check it. I wrote about the bigger deliverability picture in Six Out of Ten, and this is the hands-on part.
Each record answers a different question, and they only work properly together.
| Record | Where it lives | What it proves |
|---|---|---|
| SPF | A TXT record on the domain in the envelope sender (the return path) | The server that sent the message is allowed to send for that domain |
| DKIM | A TXT record (or a CNAME pointing to one) at selector._domainkey.yourdomain.com | The message was signed by that domain and wasn't changed on the way |
| DMARC | A TXT record at _dmarc.yourdomain.com | SPF or DKIM passed for a domain that matches the visible From address, and what to do if neither did |
That last column matters more than it looks. SPF and DKIM can both pass for a domain your reader never sees, like your email provider's. DMARC is the one that ties a passing check back to the domain in your From line.
SPF
SPF is a list of the servers allowed to send mail for a domain.
The receiving server looks at the domain in the envelope sender (sometimes called the return path or bounce address, which is often different from the From address), fetches that domain's SPF record, and checks whether the sending server's IP is on it.
A typical record looks like this:
example.com. TXT "v=spf1 include:_spf.google.com include:amazonses.com ~all"
Each include: pulls in another service's list. The ~all at the end says anything not listed should be treated as a soft fail. -all is stricter and says to fail it outright, and both are fine once DMARC is in place.
A couple of rules catch people out.
A domain can only have one SPF record, so adding a second TXT record that starts with v=spf1 breaks both of them. You merge them into one instead.
And SPF allows at most 10 DNS lookups, counting every include:, a, mx, ptr, exists, and redirect=, plus the lookups inside the records you include. Go past 10 and SPF returns an error for every message.
A lot of newsletter platforms send with their own return path domain, so your root SPF record doesn't come into it at all. That's normal, and it's why DKIM does most of the work for newsletters.
DKIM
DKIM signs each message with a private key your email provider holds, and you publish the matching public key in DNS.
The receiver checks the signature against the key, which proves the message came from someone holding that key and that the body and key headers weren't changed in transit.
The key lives under a selector, a name your provider picks, so a record sits at a name like k2._domainkey.example.com. Most newsletter platforms have you add a CNAME there that points to a key they host, which lets them rotate keys without asking you to change DNS:
k2._domainkey.example.com. CNAME dkim2.mcsv.net.
If you publish the key yourself, it's a TXT record:
s1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA..."
The signature on each message carries a d= tag (the domain that signed it) and an s= tag (the selector). The d= domain is what DMARC compares with your From address.
DMARC
DMARC is the policy record. It tells receivers to check whether SPF or DKIM passed for a domain that lines up with your From address, what to do with mail that fails, and where to send reports. A good first record looks like this:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
p=none means "don't do anything different yet, just send me reports." rua= is where the daily aggregate reports go. Once the reports show all your real mail passing, you move to quarantine and then reject.
Alignment
This is the part most explanations skip. DMARC passes when at least one of these is true:
- SPF passed, and the envelope sender's domain matches the From domain.
- DKIM passed, and the signature's
d=domain matches the From domain.
By default the match is relaxed, so news.example.com lines up with example.com because they share the same organizational domain. A newsletter can pass SPF and DKIM and still fail DMARC if both passes are for your provider's domain.
Setting up a verified or authenticated domain in your provider is what fixes that, because it makes the provider sign with your domain.
Setting It Up for Kit
In Kit, the setting is called a verified sending domain. Kit gives you a short list of CNAME records to add at your DNS provider, with host names along the lines of ckespa and cka._domainkey, and then you click Validate.
Kit can also add them for you if your DNS provider supports its automatic setup.
The CNAMEs cover both DKIM and the return path, so SPF and DKIM both end up aligned with your domain and you don't need to touch your root SPF record.
Kit's help docs don't say it adds a DMARC record for you, so check for one at _dmarc and add the starter record above if it's missing.
Copy the exact names and values from Kit's screen, since some are unique to your account. If your DNS is on Cloudflare, set each CNAME to "DNS only" (the grey cloud), because a proxied CNAME won't resolve to the key and DKIM fails.
Setting It Up for Beehiiv
Beehiiv lets you send from your own domain on its paid plans. To set it up, go to Settings, then Domains, and choose Set up custom domain. It asks for the domain or subdomain you'll send from, like newsletter.example.com, and the address you'll use in the From line.
Beehiiv then gives you 3 CNAME records to add, one for SPF and 2 for DKIM. Like Kit's, they put both checks on your own domain, so they line up with your From address and your root SPF record stays as it is.
You can add them by hand, or let Beehiiv's setup partner Entri add them after you sign in to your DNS provider.
Beehiiv is stricter about DMARC. Every publication sending from a custom domain needs a valid DMARC record, and Beehiiv only adds one for you on its own subdomains.
The Domains page has a wizard that writes one, or you can use the starter record above at _dmarc. If your domain already has a DMARC record, keep that one.
Verification usually takes a few hours but can take up to 72. Wait until every record shows Live on the Domains page before you send from the new domain. On Cloudflare, set each Beehiiv record to "DNS only" here too, since Beehiiv can't see proxied records.
Setting It Up for Mailchimp
Mailchimp first has you verify that you own the domain, then authenticate it from the Domains page. Its manual setup asks for 2 CNAME records and 1 TXT record. The CNAMEs are for DKIM and usually look like this:
k2._domainkey.example.com. CNAME dkim2.mcsv.net.
k3._domainkey.example.com. CNAME dkim3.mcsv.net.
The TXT record is DMARC, at _dmarc. If you already have a DMARC record, keep the one you have, since a domain should only have one.
Mailchimp's guide doesn't ask you to add an SPF include for it, and the return path stays on Mailchimp's own domain. So for Mailchimp, DMARC passes through DKIM alignment, which is why those 2 CNAMEs are the records that matter.
A common slip: some DNS providers add your domain to whatever you type in the name field, so pasting k2._domainkey.example.com creates k2._domainkey.example.com.example.com. Enter just k2._domainkey if yours does that.
Setting It Up for Amazon SES
SES is more hands-on, which suits it if you're sending from your own app. Verify your domain as an identity and turn on Easy DKIM, and SES gives you 3 CNAME records like this one:
abcdef1234._domainkey.example.com. CNAME abcdef1234.dkim.amazonses.com.
There's one of these per token, with your own tokens in place of abcdef1234.
That gives you aligned DKIM. By default, SES uses an amazonses.com return path, so SPF passes for Amazon's domain and doesn't align with yours. To fix that, set a custom MAIL FROM domain, a subdomain like bounce.example.com, and add an MX record and an SPF record for it:
bounce.example.com. MX 10 feedback-smtp.us-east-1.amazonses.com.
bounce.example.com. TXT "v=spf1 include:amazonses.com ~all"
Use the region you send from in the MX host. With both in place, SPF and DKIM align with your domain, and you add the DMARC record at _dmarc.example.com like any other setup.
What Gmail, Yahoo, and Outlook Require
The big mailbox providers now publish their rules, and they mostly agree.
| All senders | Bulk senders | |
|---|---|---|
| Gmail | SPF or DKIM, valid forward and reverse DNS for sending IPs, TLS, spam rate under 0.3% | SPF and DKIM, DMARC (at least p=none) with the From domain aligned, one-click unsubscribe, spam rate under 0.1% and never 0.3% |
| Yahoo | SPF or DKIM, valid forward and reverse DNS, spam rate under 0.3% | SPF and DKIM, DMARC (at least p=none) that passes with relaxed alignment, one-click unsubscribe, unsubscribes honored within 2 days |
| Outlook.com | Its general sender guidelines | SPF and DKIM must both pass, DMARC at least p=none aligned with one of them |
Gmail counts you as a bulk sender once you send close to 5,000 messages to personal Gmail accounts in a day, and once you're classified that way it's permanent.
Outlook.com's rules cover its consumer addresses (Outlook, Hotmail, and Live) for domains sending more than 5,000 a day, and Microsoft started enforcing them in May 2025, first by sending failing mail to Junk. Its support pages now describe failing mail being rejected with 550 5.7.515.
Google started ramping up enforcement in November 2025, so non-compliant mail now gets temporary or permanent rejections instead of a quiet trip to spam.
For one-click unsubscribe, Gmail wants a List-Unsubscribe header with an HTTPS link plus List-Unsubscribe-Post: List-Unsubscribe=One-Click, along with a visible link in the body. Kit and Mailchimp add these headers for you. With SES you add them yourself.
If your list is anywhere near 5,000 Gmail readers, set this up as though the bulk rules already apply to you.
The DNS side usually takes about 20 minutes, and nothing about it hurts a smaller sender.
What About BIMI and the Others?
BIMI is the record that puts your logo next to your name in the inbox. It's a TXT record at default._bimi that points to your logo, saved in a strict SVG format called SVG Tiny PS:
default._bimi.example.com. TXT "v=BIMI1; l=https://example.com/bimi-logo.svg"
It only works once DMARC is set to quarantine or reject, so p=none doesn't count, and Google also wants pct left at 100. Yahoo will show a logo from the record alone. Gmail and Apple Mail want a paid certificate that proves the logo is yours, which for Gmail means a Verified Mark Certificate or a Common Mark Certificate.
That makes BIMI something to come back to once your DMARC reports have been clean for a while.
You may also come across MTA-STS and TLS-RPT. They protect mail coming in to your domain, so they don't affect a newsletter you send. ARC gets added by forwarding services and mailing lists as they pass a message along, and there's no record for you to publish.
Checking It With the Tool
Once the records are in, run your domain through the Email Deliverability Check. It looks up your SPF record (and counts its DNS lookups), tries the common DKIM selectors, and reads your DMARC policy, with a plain-English note for anything that's off.
If it can't find your DKIM key, open an email you've sent, find the s= value in the DKIM-Signature header, and enter that as the selector.
If a record you just added doesn't show up yet, the DNS Lookup tool can ask 4 public resolvers at once, so you can see whether the change has spread or there's a typo in the name. Names with underscores like _dmarc.example.com work there too.
The DNS check tells you the records exist and are well formed. The real proof is a message in an inbox with spf=pass, dkim=pass, and dmarc=pass in its headers.
To see them, send a test to your own Gmail account, open the message, and choose Show original from the menu.
A Quick Checklist
- One SPF record on each domain that sends, under 10 lookups.
- DKIM set up in your newsletter platform with your own domain, not the platform's.
- A DMARC record at
_dmarcwithp=noneand anrua=address to start. - A test email sent to Gmail and Outlook, with every check passing in the headers.
- A reminder to move DMARC to
quarantineonce a few weeks of reports look clean.