Home · Email authentication by platform · Updated 18 November 2026

beehiiv SPF, DKIM and DMARC setup

Short answer: In beehiiv go to Settings → Domains → Set up custom domain and enter an email domain or subdomain. Add the ownership TXT record, then the records beehiiv shows for your email domain (beehiiv handles SPF and DKIM with CNAME records). Then add a DMARC TXT record at _dmarc: beehiiv says every publication sending from a custom domain needs one.

Ad This page contains affiliate links (#Ad) to beehiiv and Warmy. CourseSignal is run by Urban Huntsman Ltd, which earns a commission if you sign up through them, at no extra cost to you. This guide is free and based only on the platform’s own help articles. Links to the platform’s docs are plain links.

You do not need a custom domain to send with beehiiv; beehiiv adds DMARC automatically for its own subdomains. If you send from your own domain, beehiiv says SPF and DKIM are handled by CNAME records you add during setup, and DMARC is something you add yourself (beehiiv: Setting up DMARC).

Check your domain first, and again when you finish. The free CourseSignal email authentication checker shows the SPF, DKIM, DMARC and MX records your domain publishes today, so you can spot an existing SPF or DMARC record before you add another. beehiiv generates its DKIM record names per domain, so take the selector from the DKIM record beehiiv shows you. Then run the email blacklist checker on the same domain. Both run free with no sign-up.

Records you will add

beehiiv generates each record for your domain and groups them on the setup screen. Copy the Type, Name and Value of each one.

PurposeTypeName / hostValue
Domain ownershipTXTCopy from your beehiiv dashboardCopy from your beehiiv dashboard
Email domain (SPF and DKIM)CNAMECopy from your beehiiv dashboardCopy from your beehiiv dashboard
Branded link (2 records)CNAMECopy from your beehiiv dashboardCopy from your beehiiv dashboard. beehiiv asks you to replace one value partway through setup
DMARCTXT_dmarcbeehiiv’s example: v=DMARC1; p=none; rua=mailto:[your report address];. Generate yours with beehiiv’s DMARC wizard

Record groups from beehiiv: How to add your custom domain DNS records manually. beehiiv says the DMARC example is only an example using p=none; your record depends on the options you choose in its wizard.

Step by step in beehiiv

  1. Click Settings in the bottom-left corner of your dashboard, then Domains → Set up custom domain.
  2. For email, enter your Email domain or subdomain (beehiiv’s example is email.yoursite.com) and your Sending address, then click Next.
  3. Choose Entri (sign in to your domain provider and Entri adds the records) or I’ll add the records myself.
  4. Manual: copy the ownership TXT record into your DNS, then click Verify ownership. When it shows Verified, click Next.
  5. Add each group’s records (email domain, branded link) and click Verify record on that group. You can click Done for now; beehiiv keeps checking for up to 72 hours.
  6. If the branded link shows Needs attention, click Replace record, update that one record’s value at your DNS provider, and click Verify updated record.
  7. On the Domains page, click Create a DMARC record in the banner and add the record (next section). Wait until everything shows Live before you send.

DMARC

beehiiv: “As of February 2024, all beehiiv accounts using a custom domain must have a valid DMARC record configured” (beehiiv: Setting up DMARC for a custom domain).

Add a TXT record with the host _dmarc and the value from beehiiv’s DMARC wizard. beehiiv’s example is v=DMARC1; p=none; rua=mailto:…;. beehiiv notes that the reporting address is publicly visible in DNS, so it suggests a dedicated address rather than a personal inbox.

beehiiv says propagation can take from a few seconds to 72 hours.

Things beehiiv warns about

After the records verify

  1. Run your domain through the email authentication checker. Enter your DKIM selector if you know it.
  2. Send a test email to an address you control, open the original message and confirm SPF, DKIM and DMARC show “pass”.
  3. Check the domain on the email blacklist checker.
  4. Keep the records in place. Removing them later breaks authentication for mail already in flight and for future sends.

Passing authentication shows your mail is allowed to use your domain. It does not guarantee the inbox: list quality, engagement and complaint rates still matter.

Not on beehiiv yet?

If you are choosing a newsletter platform, you can start with beehiiv Ad Commission if you use this link..

People who sign up through this link get a 14-day trial and 20% off their first 3 months on a paid plan, according to beehiiv’s partner programme page (beehiiv.com/partners, checked 18 November 2026 (GMT)). Confirm the current offer on beehiiv’s site.

Fix deliverability over time

Authentication is only the first step. Warmy is a paid email warm-up and inbox-placement tool. It gradually sends and receives mail from a connected mailbox to help build sender reputation, and it also offers placement tests. It does not replace SPF, DKIM or DMARC, and it does not guarantee inbox placement.

Warmy’s pricing page lists a 7-day free trial with no credit card required. Its FAQ says the trial is limited to one mailbox and about 15–50 emails a day, which is not long enough to finish warming a new domain. Plans are volume-based. Confirm current plans and trial terms on Warmy’s site before you sign up.

Checked on warmy.io/pricing and warmy.io/faq, 18 November 2026 (GMT). This is a separate deliverability tool. It is not a substitute for authentication, list hygiene, a pre-send placement test, or HighLevel.

FAQ

Does beehiiv require DMARC?

Yes, for custom domains. beehiiv says all accounts using a custom domain must have a valid DMARC record. If you send from a beehiiv subdomain, beehiiv handles DMARC.

What records does beehiiv need for a custom email domain?

An ownership TXT record, the CNAME records beehiiv generates for your email domain (which cover SPF and DKIM), two branded link CNAME records, and a DMARC TXT record you add yourself.

How long does beehiiv domain verification take?

beehiiv says verification usually takes a few hours but can take up to 72 hours, and to wait until everything shows Live before sending.

My records are correct but beehiiv cannot see them. Why?

If you use Cloudflare, check the proxy status. beehiiv cannot detect records set to Proxied; set them to DNS only.

Sources (checked 18 Nov 2026)

Every record and step above comes from these official help articles, read on 18 November 2026 (GMT). Platforms change their setup screens, so if your dashboard shows something different, follow the dashboard.

Related: SPF, DKIM and DMARC setup by platform · Email authentication checker · SPF checker · DKIM checker · DMARC checker · Email blacklist checker · Deliverability checklist.