Suped

How to set up DMARC/DKIM/SPF for Keap

Published 23 Aug 2026
Updated 25 Oct 2026
14 min read
Summarize with
How to set up DMARC, DKIM, and SPF for Keap
Updated on 25 Oct 2026: We updated Keap authentication guidance for Contact Owner automations and current DMARC policies.
Keap requires DKIM authentication for a custom sending domain and an applicable DMARC policy. Keap also recommends include:infusionmail.com in the domain's single SPF TXT record, but SPF is not its primary sending requirement. Publish the account-specific CNAME records, confirm the domain in Keap, then test a real message for DMARC alignment through SPF or DKIM before enforcing DMARC.
Keap Pro and Max place this workflow under Settings > Domains. Max Classic and Ultimate use Marketing > Settings > Email Authentication. The DNS values are account-specific, so copy the records shown in the account instead of reusing values from another domain or an old setup.

Add your domain

  1. Open settings: In Keap Pro or Max, click the profile icon, choose Settings, then open Domains. In Max Classic or Ultimate, open Marketing, choose Settings, then Email Authentication.
  2. Choose the domain: Under Email, click Connect this domain beside the suggested business domain, or click Connect Email Domain to enter another domain.
  3. Use a custom domain: Enter the domain used after the @ in the visible From address. Do not use a free mailbox domain because you cannot publish its DNS records.
  4. Select DNS hosting: Choose the company that hosts the domain's authoritative DNS. Select Other if it is absent from Keap's list, then continue.
  5. Protect existing DMARC: If a DMARC policy already applies, leave Create or Update DMARC Record unchecked in Keap. Never publish a second DMARC TXT record at the same hostname.
Use the exact domain shown in campaign From addresses. If campaigns use example.com and news.example.com, authenticate each domain Keap uses rather than assuming one setup covers every subdomain.
Keep the Keap setup tab open while editing DNS. Keap normally presents one return-path CNAME and two DKIM CNAME records. The labels and targets can differ by account, so copying is safer than typing.
Keap email domain authentication settings with Connect Email Domain controls
Keap email domain authentication settings with Connect Email Domain controls
The connected domain must also match the user or sender address configured in Keap. After authentication, update any profile, campaign, or automation still using an address on another domain.
Do not delete an existing sender's DNS record while adding Keap. SPF must be merged, but distinct DKIM selectors from different senders can coexist.

Set up SPF

  1. Find the SPF record: In authoritative DNS, locate the TXT record at the sending domain whose value starts with v=spf1.
  2. Authorize Keap: Add include:infusionmail.com before the final all mechanism, as recommended in Keap's SPF instructions. Complete DKIM setup before relying on SPF results.
  3. Merge, never duplicate: Edit the existing SPF value. A second v=spf1 TXT record causes SPF PermError.
  4. Publish the return path: Add the return-path CNAME Keap displays. Do not add a separate SPF TXT record at that CNAME hostname.
  5. Check lookup count: Keep evaluation within SPF's limit of ten DNS-querying terms, including nested includes.
A domain with no other sender can use the first record below. A domain that already authorizes another sender must keep those mechanisms and insert Keap before the final ~all or -all.
Keap SPF examplesDNS
v=spf1 include:infusionmail.com ~all v=spf1 include:_spf.example.net include:infusionmail.com ~all
Do not copy the merged example verbatim. Keep the mechanisms already required by your mailbox provider and every other legitimate sender. Remove obsolete mechanisms only after proving that the related service no longer sends mail.
SPF evaluates the envelope sender domain shown in Return-Path. Adding include:infusionmail.com to the visible From domain's SPF record does not change that envelope domain or create DMARC alignment. Publish Keap's supplied return-path CNAME and verify the actual Return-Path in a new message.

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
Check the domain whose SPF TXT record you edited, then check the actual Return-Path domain shown in a Keap test message. Confirm one SPF policy per hostname, valid syntax, and no lookup-limit or recursion error.
If SPF passes without DMARC alignment, compare the Return-Path with the visible From domain. Default relaxed alignment requires the same organizational domain; aspf=s requires an exact domain match. An aligned DKIM pass still satisfies DMARC while you investigate the return-path setup.
Do not create a second SPF record
Two SPF TXT records at the same hostname do not provide extra authorization. They produce a permanent SPF evaluation error. Merge Keap into the existing record.

Set up DKIM

  1. Copy both selectors: On Keap's DNS records screen, copy each DKIM CNAME with the built-in copy control. The hosts commonly resemble appname1._domainkey and appname2._domainkey.
  2. Create CNAME records: For each row, place Keap's Name in the DNS Host field and Keap's Value in the Target or Points to field.
  3. Avoid doubled domains: If the DNS provider automatically appends the zone name, enter only the host portion. Check the saved fully qualified hostname before continuing.
  4. Disable proxying: Set each authentication CNAME to DNS-only when the DNS host offers a proxy toggle. A proxied CNAME cannot be resolved as Keap expects.
  5. Return to Keap: Save the DNS changes, return to the open wizard, then click Confirm or Finish.
Keap holds the private keys and signs outgoing messages. The CNAME records delegate public-key lookup to Keap, so there is no private key to upload and no TXT public key to invent.
The two selectors allow key rotation without interrupting authentication. Publish both even if only one selector appears in the first test message.
Keap domain authentication DNS records with one return-path and two DKIM CNAMEs
Keap domain authentication DNS records with one return-path and two DKIM CNAMEs
Do not overwrite another sender's DKIM selector. If a hostname conflicts, use Keap's Conflict with your domain? option to generate a different app prefix, then publish the new values.
After Keap reports Connected, send a fresh campaign test. DKIM must pass with DMARC alignment: the d= signing domain must share the visible From address's organizational domain under relaxed alignment, or match the From domain exactly when adkim=s.
DKIM values are account-specific
Copy every host and target from the active Keap wizard. Values found in another account, an old screenshot, or a forum post can resolve correctly while signing for the wrong tenant.

Set up DMARC

  1. Check for DMARC: Check _dmarc on the visible From domain and whether a parent policy applies before creating anything. Publish no more than one DMARC TXT record at each policy hostname.
  2. Keep enforcement: If the domain already uses p=quarantine or p=reject, keep that policy. Add Keap authentication and monitoring without weakening it to p=none.
  3. Start monitoring: If no policy applies, create a TXT record at the sending domain's _dmarc hostname using the monitoring record below and your own reporting address.
  4. Use a live mailbox: Ensure the rua destination can receive aggregate reports. If using a reporting platform, use the unique destination it supplies.
  5. Save as TXT: For this manual setup, publish the policy as a TXT record through authoritative DNS, outside Keap's campaign editor. Manage an existing hosted policy through its provider instead.
Start with p=none when no DMARC policy applies because it requests reports without requesting quarantine or rejection. Replace dmarc@example.com with a reporting destination you control.
Initial DMARC recordDNS
v=DMARC1; p=none; rua=mailto:dmarc@example.com
For example.com, the TXT hostname is _dmarc.example.com; for news.example.com, it is _dmarc.news.example.com. Some DNS interfaces append the zone name automatically, so enter only the relative host there to avoid a doubled domain.
Use the DMARC record generator only when you need to change the reporting address or add deliberate tags. Keep the record simple until reporting confirms every legitimate sender.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
Check the domain after DNS caches expire. Confirm one applicable DMARC policy with valid syntax and the intended rua address. DNS checks do not prove mailbox delivery. If rua uses a different organizational domain from the policy record, confirm the recipient authorizes external reports as specified in RFC 9990; otherwise, receivers ignore that destination.
Follow Keap's authentication instructions for account navigation and CNAME values. Review generated DMARC policy tags separately, because the wizard's percentage controls do not establish a safe enforcement rollout.
Keap DMARC setup controls for the policy and aggregate reporting address
Keap DMARC setup controls for the policy and aggregate reporting address
When a DMARC policy already applies, leave Create or Update DMARC Record unchecked. If Keap offers p=quarantine; pct=5 for a new policy, do not rely on the percentage: IANA's DMARC registry marks pct historic. Receivers following RFC 9989 ignore pct, so quarantine can apply to all DMARC failures. Use p=none until legitimate senders are verified.
DMARC passes when at least one aligned path passes: SPF with an aligned Return-Path, or DKIM with an aligned d= domain. Configure and monitor both so a temporary problem on one path does not remove all authenticated coverage.

Verify and troubleshoot

  1. Finish in Keap: Return to the domain wizard after saving DNS and click Finish or Confirm.
  2. Read the status: Pending is normal during DNS propagation. Connected means Keap resolved the required records.
  3. Send a real test: Send through the same Keap campaign or automation path used in production, using a From address on the connected domain.
  4. Inspect authentication: Confirm SPF pass, DKIM pass, and DMARC pass. Also confirm that at least one passing identifier meets the visible From domain's DMARC alignment requirements.
  5. Retest every path: Test broadcasts, automated follow-ups, and transactional messages if the account sends through more than one Keap path.
Keap advises allowing 24-48 hours for DNS verification. If the domain remains Pending after that point, open its edit control, walk through the wizard again, and confirm the records so Keap performs another lookup.
The fastest end-to-end check is a message generated by Keap itself. Read the receiving server's Authentication-Results header and compare smtp.mailfrom, the DKIM d= domain, and the visible From domain. DNS-only checks cannot prove the final message passed DMARC.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
Send the tester address a new Keap message, then review the authentication results. A forwarded copy is unsuitable because forwarding can alter SPF and hide the original delivery path.
An SPF pass for infusionmail.com does not provide DMARC alignment with your business domain. If Keap's Return-Path still uses that domain, check the supplied return-path CNAME and confirm the DKIM signing domain. A passing DKIM signature with DMARC alignment is enough for DMARC to pass.

Result

Likely cause

First fix

Pending
Missing or mismatched CNAME
Check the saved hostname and target
SPF error
Duplicate SPF record or lookup limit
Use one SPF record and check nested includes
DKIM fail
Wrong selector or target
Match the message's s= and d= values to Keap's DNS records
DMARC fail
Neither passing identifier meets alignment requirements
Compare From with Return-Path and DKIM d=
Common Keap authentication failures and the first corrective action.
When a CNAME looks correct but stays Pending, check for a duplicated zone name, proxying, stray whitespace, or a conflicting record at the same host. A CNAME cannot coexist with another record type at that exact hostname.
Once authentication passes, change the Keap profile and every campaign sender to an address on the connected domain. A Connected domain does not repair an automation that still sends with a different From domain.
Keap Domains page showing Connected and Pending statuses
Keap Domains page showing Connected and Pending statuses

Fix Contact Owner automation senders

In Keap Ultimate and Max Classic, automations using Contact Owner as the sender can fail when the owner's profile email uses a domain that is not Connected. Authenticating a domain does not change existing owner assignments.
  1. Check each sending user's email under Admin > Users against the domains marked Connected.
  2. Update profiles that use unauthenticated domains. In Marketing > Settings > Template Defaults, select an authenticated Default User for unassigned contacts.
  3. In CRM > Contacts, filter by Owner ID for affected users or Unassigned. Review the selected contacts before using Actions > Mass Update Contacts to set the intended Owner ID.
  4. Test Contact Owner sending for both assigned and unassigned contacts after saving.
Follow Keap's Contact Owner instructions for edition-specific navigation.

Monitor Keap authentication and DNS changes

  1. Collect reports: Send DMARC aggregate reports to a system that parses XML and retains source history. A mailbox full of raw XML is not an operational alerting process.
  2. Verify Keap as a source: Label the Keap sending source only after matching its DKIM domain, Return-Path, and observed sending data.
  3. Alert on change: Trigger alerts when Keap's aligned pass rate drops, a new unverified source appears, or the public DNS record changes.
  4. Watch quiet automations: Keep low-volume follow-ups visible because a broken selector can remain unnoticed between large campaigns.
Suped, our DMARC reporting platform, turns aggregate reports into source-level authentication results and flags issues for investigation. Use its DMARC monitoring to compare Keap's SPF and DKIM results with other sending sources and investigate changes after DNS edits.
For multiple domains, agencies and MSPs can use Suped's multi-tenant dashboard to keep each client's Keap source, policy state, and alert history separate. That prevents one shared reporting mailbox from mixing unrelated domains.
Set alert recipients to people who can change both Keap and DNS. An alert without access to one side of the configuration often waits while campaigns keep sending unauthenticated mail.
Keep weekly summaries for trend review. DMARC aggregate reports normally cover daily activity, so authentication alerts depend on reports arriving. Use DNS change monitoring and fresh test messages for separate checks between reports.

Choose a DMARC enforcement policy

  1. Keep stronger policies: If the domain already uses quarantine or reject successfully, do not reduce enforcement while adding Keap.
  2. Observe a full cycle: At p=none, collect enough reports to include normal Keap campaigns, infrequent automations, and every other legitimate sender.
  3. Fix every valid source: Before p=reject, require a valid DKIM signature with DMARC alignment; SPF alone is vulnerable to forwarding. Keep Keap's selectors and supplied return-path CNAME working.
  4. Quarantine first: Move to p=quarantine after legitimate senders pass, then review delivery results before deciding on p=reject. Do not rely on pct to limit enforcement.
  5. Evaluate reject: Set p=reject only after checking every legitimate sender and indirect mail flow. Keep reporting enabled after enforcement.
For a dedicated Keap sending domain, review a full sending cycle, including seasonal or monthly automations. RFC 9989 advises against p=reject for general-purpose domains whose users post to Internet mailing lists. Assess forwarding and mailing-list delivery before choosing reject for a shared business domain.
Example reject record after validationDNS
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Suped's hosted DMARC workflow manages policy changes while keeping reporting active. Hosted DMARC lets a team manage several Keap domains without repeated manual TXT edits. Check each domain's reports before applying a stricter policy.
Ready for reject
  1. Keap authenticated: Current campaign tests pass DMARC through a valid DKIM signature with alignment.
  2. Sources owned: Every recurring source has a business owner and authentication path.
  3. Reports stable: No valid source depends on unauthenticated delivery.
  4. Rollback prepared: The current record and DNS access are documented.
Hold enforcement
  1. Unknown source: Unexplained traffic might still be business mail.
  2. Intermittent DKIM: One Keap path signs correctly while another does not.
  3. SPF error: The domain has duplicate records or exceeds lookup limits.
  4. No alerts: Nobody will see an authentication regression quickly.
Keep rua reporting in the reject record to identify new senders and Keap configuration drift. A p=reject policy requests rejection of DMARC failures; receivers apply their own handling rules.
Review subdomain policy separately when Keap sends from a subdomain. The organizational policy can inherit, but an explicit subdomain DMARC record overrides that inheritance and must be monitored on its own.

Keap authentication FAQ

Keap and Infusionsoft names can both appear in older DNS guidance and message headers. Use the current Keap account values for setup, then use header identifiers only as evidence during diagnosis.

Keap requires DKIM domain authentication and an applicable DMARC policy. SPF is recommended rather than Keap's primary sending requirement. Its current instructions recommend adding include:infusionmail.com to the domain's single SPF record and publishing all supplied authentication CNAMEs.

Use include:infusionmail.com rather than copying IP addresses from old forum posts. Keap, formerly Infusionsoft, manages a shared IP pool whose addresses change. Follow the current SPF instructions and keep the mechanisms required by other active senders.

No. A Connected domain and passing authentication results do not guarantee inbox placement. Recipient filtering also considers sending reputation and engagement, so authenticated mail can still reach spam.

Keap advises allowing 24-48 hours for DNS verification. After that, check for a doubled domain name, proxied CNAME, wrong target, stray whitespace, or a conflicting record. Reopen the domain in Keap and confirm the records again to trigger another check.

Yes. A passing DKIM signature with DMARC alignment satisfies DMARC even when SPF lacks alignment. Check the actual Return-Path and supplied CNAME before changing SPF; adding an include at the visible From domain does not change the envelope sender.

Yes, after validating legitimate senders and indirect mail flows. Retain an existing working policy while adding Keap. For a dedicated sending domain, monitor first and evaluate quarantine before reject. For domains used by people posting to Internet mailing lists, follow RFC 9989's interoperability guidance. Keep aggregate reporting active.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing