How to set up SPF, DKIM and DMARC in SendPulse
Setting up domain authentication in SendPulse takes five steps: generate the records in your account, add the SPF record, add the DKIM record, publish a DMARC record, and check the result. SendPulse generates the SPF and DKIM records and, according to its deliverability guide, offers a DMARC record on the same screen; with DMARC, the policy you start with matters most. All three are TXT records at the company that hosts your domain’s DNS.
- Generate the SPF and DKIM records in SendPulse’s domain settings.
- Add SPF: a TXT record on the root of the domain, or SendPulse’s include merged into the SPF record you already have.
- Add DKIM: a TXT record named sign._domainkey.
- Publish DMARC: a TXT record named _dmarc, starting with the none policy.
- Check the records in SendPulse and with an outside lookup tool.
Only one setup is needed even if you use both email campaigns and SMTP. The two share one list of authenticated domains, so records added for one serve the other.
Email and SMTP share one list of authenticated domains, so the records are added to DNS once for both; the plans set how many domains you can authenticate, the higher limit applies, the free email plan allows 1 domain and the free SMTP plan 2, and each subdomain counts as a separate domain.
Step 1: Generate the records in SendPulse
Open Email > Settings > Domain settings, click Activate in the Authenticated domain section and enter the bare domain, such as example.com. SendPulse then shows a name and a value for the SPF record and for the DKIM record. Keep that screen open while you work in your DNS provider’s panel.
SendPulse generates a domain’s SPF and DKIM records under Email > Settings > Domain settings: in the Authenticated domain section click Activate, enter the domain as example.com without http:// or www, and click Get SPF and DKIM Records, then copy the name and value of each record.
Authenticate the domain you send from. If your sender address is news@example.com, the domain is example.com; if you send from a subdomain such as mail.example.com, authenticate that subdomain, and remember that it counts toward your plan’s domain limit.
SendPulse’s help center says the authenticated domain must match the domain of the sender address to pass spam filters.
Step 2: Add the SPF record
The SPF record tells receiving servers which services may send mail for your domain. Add it as a TXT record on the root of the domain, named @ or the domain itself depending on your host. A domain can have only one SPF record, so if one already exists, add SendPulse’s include to it rather than creating a second.
SendPulse’s SPF record is a TXT record named @ or yourdomain.com with the value v=spf1 include:mxsspf.sendpulse.com +a +mx ~all; a domain that already has an SPF record adds include:mxsspf.sendpulse.com to that record, next to the other services that send for it.
Look for an existing record before you save. Google Workspace, Microsoft 365, a CRM or a help desk that sends as your domain may already have an SPF record there; two separate SPF records make SPF fail for both.
Step 3: Add the DKIM record
DKIM signs each email so the receiving server can confirm it came from your domain and was not changed on the way. Add SendPulse’s DKIM record as a TXT record named sign._domainkey and paste the value from your account, not the example key printed in the help article.
SendPulse’s DKIM record is a TXT record named sign._domainkey whose value, a public key starting v=DKIM1; k=rsa; p=, is shown in your SendPulse account and is pasted without quotes; the key printed in the help article is only an example.
Many DNS panels add the domain to the name for you. In cPanel the full name becomes sign._domainkey.yourdomain.com; if your host does this, enter only sign._domainkey, or the record ends up under the wrong name.
Step 4: Publish a DMARC record
DMARC tells receiving servers what to do with mail that claims to be from your domain but fails SPF and DKIM, and sends you reports about it. SendPulse’s DMARC guide says to set up SPF and DKIM first, publish a DMARC TXT record with the policy none, and tighten the policy only after reading the reports.
SendPulse’s DMARC guide says to list every legitimate source of email from the domain, set up SPF and DKIM first, publish a DMARC TXT record in the domain’s DNS with the policy none, and move to quarantine or reject after reading the reports, although the guide’s own example record uses p=reject; under reject, mail from senders not on the allow list, CRM systems and email services included, is rejected too.
SendPulse’s deliverability guide says the domain settings screen that generates the SPF and DKIM records also offers a DMARC record under Advanced Options, to be copied to DNS like the other two.
Under a DMARC none policy failing mail still reaches the inbox and the domain owner gets reports, quarantine sends it to spam, and reject stops it from being delivered.
Use the record from Advanced Options if your account shows one, or write your own. A first record looks like v=DMARC1; p=none; rua=mailto:dmarc@example.com, published as a TXT record named _dmarc. Replace the address with a mailbox you read, or with a DMARC report service’s address.
In a DMARC record, rua is the address for aggregate reports, usually sent daily as XML files, and ruf the address for per-message failure reports; each address takes the mailto: prefix, and without rua no aggregate reports arrive.
Whichever you use, check its policy before you publish it: SendPulse’s DMARC guide prints an example with p=reject. That is the end point of the rollout, not the place to start: under reject, any service you forgot to cover in SPF or DKIM has its mail refused.
Step 5: Check the records
Back in SendPulse, open the domain’s settings and click Check DNS records. A correct, propagated record shows a green check mark, and the domain’s status changes from Awaiting confirmation to Connected. Activation can take a while, so a record that fails in the first minutes is not necessarily wrong.
SendPulse’s help center says each record can take up to 24 hours to become active, depending on the host; Check DNS records in the domain’s settings then shows a green check mark next to each record and the status changes from Awaiting confirmation to Connected, and MxToolbox or Google Admin Toolbox can check the records from outside.
Check from outside as well: MxToolbox’s SPF Lookup on your domain, its DKIM Lookup with your domain and the selector sign (yourdomain.com:sign), and its DMARC Lookup. These show what the rest of the internet sees, which is what decides delivery.
Do you need DMARC for Gmail and Yahoo?
If you send in bulk, yes. SendPulse’s article on mailbox provider rules says Gmail, Yahoo and Outlook expect bulk senders to authenticate with SPF and DKIM and publish a DMARC record, with p=none as the accepted minimum. Gmail and Yahoo add one-click unsubscribe for marketing email and a cap on the spam complaint rate.
SendPulse’s article on mailbox provider rules says Gmail, Yahoo and Outlook require bulk senders to authenticate with SPF and DKIM and publish a DMARC record, with p=none accepted as the minimum; Gmail and Outlook apply the bulk rules at about 5,000 emails a day while Yahoo states no threshold, and Gmail and Yahoo also require one-click unsubscribe for marketing email and a spam complaint rate below 0.3%.
A sender address on a free mailbox domain cannot meet these rules, because you cannot publish records for gmail.com or yahoo.com. Send campaigns from an address on your own domain.
Some free mailbox providers, such as Yahoo and AOL, use DMARC to block campaigns sent from their addresses through other services, so SendPulse, like other email services, limits campaigns from such addresses and recommends a sender address on your own domain.
Records not verified: common fixes
When SendPulse keeps showing Awaiting confirmation, the record is usually missing from public DNS, sits under the wrong name, or carries a different value from the one in your account. Run an outside lookup first: it tells you which of the three it is. Then fix the record at your DNS host and click Check DNS records again.
- Not propagated yet. Wait for the activation period before you change anything.
- Doubled name. The record shows up as sign._domainkey.example.com.example.com because the host appended the domain; enter only sign._domainkey.
- Quotes or line breaks. Paste the key without quotes and on one line, unless your host splits long TXT values itself.
- Example key. The key in SendPulse’s help article is an example; copy yours from the account.
- Second SPF record. For SPF, merge SendPulse’s include into the existing record instead of adding another.
- Wrong DNS host. If the domain’s nameservers point elsewhere, such as Cloudflare, records added at the registrar are ignored. An NS lookup in MxToolbox shows which host is live.
If emails still land in spam after the domain shows Connected, first check the sender address. DMARC passes only when SPF or DKIM passes for the same domain as the From address, so the sender address has to be on the authenticated domain.
A sender address on a domain that is not authenticated shows No domain in SendPulse and is sent through a shared domain that does not match it, which mail clients notice and which makes spam placement more likely; on an authenticated domain a new sender address is activated without a confirmation email.
Optional: a tracking domain (CNAME)
For SMTP mail, SendPulse’s tracking links use its own domain unless you add a CNAME record that puts your domain in them, so recipients see one domain throughout the email. It is not part of SPF, DKIM or DMARC and is not needed for them to pass.
A CNAME record that replaces SendPulse’s domain with your own in tracking links is available on the SMTP Pro plan and above.
SendPulse
Where these records are used- At 1,000 subscribers
- $18/moStandard
- At 10,000 subscribers
- $78/moStandard
- Emails on Standard
- unlimited emails
- Free plan
- 500 contacts, 15,000 emails/month
One set of SPF and DKIM records covers SendPulse’s email campaigns and its SMTP service, and the account checks the records for you. Two limits matter for this setup: the free email plan allows a single authenticated domain, with each subdomain counted separately, and an own tracking domain for SMTP mail is listed from the SMTP Pro plan up. Reading DMARC reports is also up to you or a report service.
Strong points
- Email, SMS and chatbots for WhatsApp, Telegram, Instagram and Messenger run from one account
- Standard plan includes unlimited emails at every list size
- Separate free tiers for SMTP, chatbots and the course builder
Limits
- Free plan stops at 500 subscribers and keeps SendPulse branding in emails
- Pay-as-you-go email credits expire after 12 months
- SMS is billed per message on top of the plan; none is bundled
- Chatbots beyond the free allowance are a separate paid plan
- A dedicated IP is listed only for the SMTP Pro and Enterprise plans
If you are still choosing where to send from
- SendPulseYou want campaigns and transactional SMTP mail on one authenticated domain, set up once.
- Amazon SESYou send large volumes of app email from AWS and manage DNS and DMARC reporting yourself.
- PostmarkYou only need transactional email from an app and want it kept apart from any marketing mail.
Frequently asked questions
How do I set up SPF, DKIM and DMARC in SendPulse?
Go to Email > Settings > Domain settings, click Activate in the Authenticated domain section, enter your domain without http:// or www and click Get SPF and DKIM Records. Add both records at your DNS provider as TXT records, publish a DMARC TXT record starting with the none policy, then click Check DNS records in SendPulse until each record shows a green check mark.
What DNS records does SendPulse need?
Two TXT records: an SPF record on the root of the domain that includes mxsspf.sendpulse.com, and a DKIM record named sign._domainkey holding the public key shown in your account. A third TXT record, the DMARC policy, goes next to them; SendPulse’s deliverability guide says the same settings screen offers one under Advanced Options. A CNAME for your own tracking domain is optional and listed for the SMTP Pro plan and above.
Why is my SendPulse DKIM not verified?
The usual causes are a record that has not propagated yet, a name the DNS host doubled (sign._domainkey.example.com.example.com), quotes left around the key, or a key copied from the help center’s example instead of your account. Wait for the activation period, compare the record with the one in your account, and check it from outside with MxToolbox’s DKIM Lookup.
Does SendPulse require DMARC?
SendPulse’s domain check centres on SPF and DKIM, but its DMARC guide recommends publishing a DMARC record after them, starting with p=none and moving to quarantine or reject once the reports show every legitimate sender passes. The large mailbox providers are the stricter side: they expect a DMARC record from bulk senders.
Do I need DMARC to send to Gmail and Yahoo?
If you send in bulk, yes. SendPulse’s article on mailbox provider rules says Gmail, Yahoo and Outlook expect bulk senders to pass SPF and DKIM and publish a DMARC record, with p=none accepted as the minimum. A smaller sender still benefits from one: a DMARC record gives you reports on who sends mail as your domain.
Sources
Every price and limit on this page comes from the vendor’s own public pages. How we choose and check.
- SendPulse: sendpulse.com/pricing?country=us — checked September 30, 2026
- SendPulse: sendpulse.com/pricing/sms?country=us — checked September 29, 2026
- SendPulse: sendpulse.com/pricing/messengers?country=us — checked September 29, 2026
- SendPulse: sendpulse.com/pricing/edu?country=us — checked November 19, 2026
- SendPulse: sendpulse.com/pricing/smtp?country=us — checked September 29, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/email-create/free-templates-email — checked November 17, 2026
- SendPulse: sendpulse.com/features/email/templates — checked November 17, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/mailing-list-recipients/create-subscription-form — checked November 17, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/mailing-list-recipients/simple-form — checked November 17, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/mailing-list-recipients/how-send-confirmation-email-subscription — checked November 17, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/mailing-list-recipients/create-mailing-list-names-recipients — checked November 6, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/mailing-list-recipients/sources — checked November 6, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/mailing-list-recipients/manage-address-blocking — checked November 6, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/mailing-list-recipients/why-activate-mailing-lists — checked November 6, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/email-create/html-editor — checked November 6, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/general/how-send-welcome-email — checked October 20, 2026
- SendPulse: sendpulse.com/integrations/ecommerce/woocommerce — checked October 8, 2026
- SendPulse: sendpulse.com/integrations/zapier-integrations/shopify — checked October 8, 2026
- SendPulse: sendpulse.com/features/automation-360 — checked October 8, 2026
- SendPulse: sendpulse.com/features/edu — checked October 8, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/automation360/send-edu-event-messages — checked October 8, 2026
- SendPulse: sendpulse.com/pricing/edu/feed.md — checked November 19, 2026
- SendPulse: sendpulse.com/knowledge-base/edu/settings/payments-on-course-website — checked November 19, 2026
- SendPulse: sendpulse.com/knowledge-base/account-settings/accept-payments — checked November 19, 2026
- SendPulse: sendpulse.com/knowledge-base/edu/settings/promo-codes — checked November 19, 2026
- SendPulse: sendpulse.com/knowledge-base/edu/builder/create-test — checked November 19, 2026
- SendPulse: sendpulse.com/knowledge-base/edu/students/manage-notification-emails — checked November 19, 2026
- SendPulse: sendpulse.com/features/chatbot/telegram — checked October 26, 2026
- SendPulse: sendpulse.com/features/chatbot — checked November 18, 2026
- SendPulse: sendpulse.com/knowledge-base/chatbot/flow-elements — checked November 18, 2026
- SendPulse: sendpulse.com/knowledge-base/chatbot/triggers — checked November 18, 2026
- SendPulse: sendpulse.com/knowledge-base/chatbot/whatsapp/connect-whatsapp — checked November 18, 2026
- SendPulse: sendpulse.com/features/chatbot/whatsapp — checked October 23, 2026
- SendPulse: sendpulse.com/features/chatbot/instagram — checked November 18, 2026
- SendPulse: sendpulse.com/features/ai — checked October 2, 2026
- SendPulse: sendpulse.com/pricing/crm?country=us — checked October 2, 2026
- SendPulse: sendpulse.com/features/email/subscription-forms — checked October 19, 2026
- SendPulse: sendpulse.com/features/pop-up — checked October 19, 2026
- SendPulse: sendpulse.com/knowledge-base/account-settings/manage-agency-area — checked October 23, 2026
- SendPulse: sendpulse.com/partners/agency — checked October 23, 2026
- SendPulse: sendpulse.com/legal/terms — checked October 23, 2026
- SendPulse: sendpulse.com/pricing — checked November 10, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/additional/email-authentication — checked November 16, 2026
- SendPulse: sendpulse.com/knowledge-base/smtp/setup-smtp-server — checked November 16, 2026
- SendPulse: sendpulse.com/knowledge-base/email-service/general/dmarc-policy — checked November 16, 2026
- SendPulse: sendpulse.com/blog/email-deliverability — checked November 16, 2026
- SendPulse: sendpulse.com/blog/gmail-yahoo-sending-requirements — checked November 16, 2026
- SendPulse: sendpulse.com/knowledge-base/smtp/smtp-sendpulse-phpmailer — checked November 16, 2026
- SendPulse: sendpulse.com/knowledge-base/smtp/using-sendpulse-smtp-server-mailpoet-by-wordpress — checked November 16, 2026