MailerLite domain authentication: use manual setup and review each DNS record

October 15, 2026

If automatic domain authentication is slow, or your DNS provider uses social login, manual setup gives you a record-by-record route to review. Use the values from your actual MailerLite account and preserve the mail services already authorized on the domain. This guide focuses on DNS setup and Pending status, rather than repeating our newsletter language samples or weekly-newsletter plan comparison.

When to consider the manual route

MailerLite's 2026-09-26 product update describes short instructions for each manual DNS record, including where to sign in and how to create that record. It also describes switching directly to manual setup when the automatic window is slow. The announcement date is September 26; October 8 is this guide's review date, not a new release date.Sources: MailerLite product updates

The current guide concerns new MailerLite, not Legacy Classic. It says DNS-provider social login is not supported by the automatic flow and points to manual setup. Start by identifying your account version and the provider that actually manages DNS. Access to a web-hosting dashboard alone does not establish authority to change the sending domain, and authentication of email sending is separate from connecting a website's custom domain.Sources: How to authenticate a domain automatically

Match three records to your account

The official manual instructions identify DKIM as a CNAME record, SPF as TXT and domain verification as TXT. For each, match the record type, Name and Value shown in your own account with your DNS provider's fields. These are three purposes, not three interchangeable entries. Do not copy another account's values or a tutorial's sample. Never publish private account credentials or account-specific verification values as a reusable configuration.Sources: How to authenticate a domain automatically

Before changing SPF, inspect the existing policy for the same domain owner name. MailerLite's merge guide says to use one SPF policy and combine the authorized sending services when multiple services are needed. A domain already using a business mailbox and a newsletter service needs a reviewed merge, not a second independent SPF policy or blind deletion of the old one. Provider-specific instructions that suggest replacement must not override this preservation check. Other TXT purposes, including domain verification, are distinct from the SPF policy.Sources: How to merge SPF records

Pending is a state to investigate

Use the guide's Check DNS step to inspect authentication status. DNS updates may take up to 24 hours according to the documentation; that is guidance, not our measured completion time or a guarantee for your provider. If the state remains Pending, compare names and values and allow for propagation before adding more records. Successful authentication is not proof that a campaign reached an inbox, avoided spam or generated sales. Sending and inbox placement need separate tests in your own authorized environment.Sources: How to authenticate a domain automatically

Do not upgrade merely to follow this checklist

The guide does not list a new fee specifically for sending-domain authentication. An existing domain is a prerequisite; domain and mailbox purchase or renewal costs were not quoted here. The current Free baseline is 250 subscribers and 2,500 emails a month. The official FAQ dates those limits to 2026-06-16, and they already appear in our existing comparison: this is not a newly discovered October reduction. The pricing FAQ displays Comfort from $12/month and Power from $25/month, with country, final currency, tier, billing and renewal unresolved. The public 14-day no-card trial still has 250-subscriber/2,500-email limits. None of those starting offers is a reason to buy a website-domain feature for email authentication.Sources: MailerLite pricing · Free plan update FAQ · MailerLite 14-day premium trial

A careful record-review sequence

  1. Confirm new MailerLite versus Legacy Classic, your existing domain and authorized DNS access. Record which mailbox and other sending services currently use the domain.Sources: How to authenticate a domain automatically · How to merge SPF records
  2. If the automatic window is slow or the provider uses social login, consult the official manual route. Read each Name and Value from your account, not from a generic example.Sources: MailerLite product updates · How to authenticate a domain automatically
  3. Review DKIM CNAME, SPF TXT and verification TXT one by one. If SPF exists, consult the merge guide and retain the other legitimate senders before any change.Sources: How to authenticate a domain automatically · How to merge SPF records
  4. Use Check DNS and the reported state. For Pending, review the fields and propagation time instead of repeatedly adding duplicate entries.Sources: How to authenticate a domain automatically
  5. Keep a later sending/inbox test, website-domain plan choice and affiliate eligibility separate from authentication. Document what each check actually establishes.Sources: How to authenticate a domain automatically · MailerLite pricing · MailerLite Affiliate Program Terms

Two common DNS questions

Should I add a second SPF TXT entry to preserve my mailbox? No. The merge guide calls for one policy at the same owner name, reviewed to preserve the appropriate sending services.Sources: How to merge SPF records

Does authentication unlock a website's custom domain or guarantee inbox delivery? No. Those are separate feature and delivery questions; the DNS status alone does not answer them.Sources: How to authenticate a domain automatically · MailerLite pricing

Affiliate status remains separate

The public affiliate terms describe 30% on eligible initial and recurring paid subscriptions, 45-day attribution, and payment conditions of more than USD100 plus at least two active qualifying paying referrals. Tipalti must support commercial receiving. The latest retained local application note is pending as of 2026-10-04; we did not refresh native approval today. Taiwan payout and approved promotional methods remain unverified. Vendor imagery needs permission. MailerLite §6.6, rechecked on 2026-10-12, requires its explicit written permission before creating, distributing or promoting discount codes or offers. Separately, it prohibits promotion on coupon/deal/discount websites or incentivized platforms, public code display and click-to-reveal codes. No such permission is established here. This article contains ordinary official links, no verified referral CTA or exclusive code.Sources: MailerLite Affiliate Program Terms

Reviewed on 2026-10-08. We did not log in, read your DNS policy, change records, send email, buy a domain or measure verification time. Delivery, conversion, savings and revenue were not tested. Interface details, actual record values, provider access and local costs require account-specific review.

Use manual setup as a structured review of the records your account supplies. Preserve the existing senders through the SPF check, then distinguish DNS authentication from delivery testing. That lets you investigate Pending without assuming an upgrade, a duplicate record or a generic sample will solve it.

Official sources

Reviewed:

Related reading