Home/HighLevel/Features/Email/How to set up SPF DKIM and DMARC authentication in HighLevel

Conversations and Inbox

How to set up SPF DKIM and DMARC authentication in HighLevel

In short

Email authentication uses SPF, DKIM, and DMARC records to prove that messages sent from your domain are authorized. HighLevel generates the DNS values, lets you add them at your registrar, verify the setup, and align From addresses so recipient servers accept your mail.

AreaEmail · Authentication & Security
Used forDental practice, Real estate agency, Online course creator
Setup steps10 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Marketing agencies that send campaigns for clients, because authenticated sending prevents client emails from being rejected.
  • SaaS startups that use HighLevel for transactional notifications, as SPF/DKIM/DMARC ensure inbox delivery.
  • Ecommerce stores that email order confirmations, because proper authentication protects brand reputation and avoids spam blocks.

02Email authentication records, explained

The authentication feature creates SPF, DKIM, and DMARC DNS records for the domain you use to send email from HighLevel. These records tell receiving servers which sources are allowed to send on your behalf and what to do when a message fails the checks. When the records are present and correct, recipient providers such as Gmail, Outlook, and Yahoo stop rejecting your messages.

You manage the records from Settings > Email Services > Sending Domain. Adding a domain generates the exact values you need for SPF, DKIM, MX, CNAME, and DMARC. The page also provides a Verify Domain button that shows whether the platform can see each record.

After the records are verified, you must update every From address in campaigns, automations, and other outbound emails to use the authenticated domain. This alignment completes the authentication flow and allows your mail to be accepted.

03How businesses use email authentication records

  • Dental practice. Add the clinic's domain as a sending domain in HighLevel. Copy the SPF, DKIM, MX, CNAME, and DMARC values and create the matching DNS records at the registrar. Verify the domain, then change appointment reminder From addresses to use the clinic domain so Gmail delivers them.
  • Real estate agency. Set up a marketing subdomain in HighLevel, add the generated DNS records, and verify them. Update the From address on property listing drip campaigns to the subdomain, ensuring leads receive the emails without being filtered.
  • Online course creator. Configure a dedicated domain for course newsletters, add the SPF/DKIM/DMARC entries in DNS, and run the verification step. Align all webinar invitation From addresses with the authenticated domain so students receive the messages in their inboxes.

04The numbers and rules that matter

  • SPF record typically includes v=spf1 include: Spf.leadconnectorhq.com include: Mailgun.org ~all.
  • DMARC record starts with v=DMARC1; p=none.
  • SPF allows a maximum of 10 DNS lookups.
  • Only one SPF record per domain is allowed.
  • DNS propagation can take 2, 48 hours.
  • Authentication recognition by email providers can take 1 to 7 days.

05Before you start

  • Own the domain you intend to use for sending.
  • Have access to edit DNS records at your domain registrar or DNS hosting provider.

06How to set up and use email authentication records in HighLevel

Set up email authentication

  1. Open Settings > Email Services > Sending Domain and click Add Domain.
  2. Enter your domain name and submit to generate authentication records.
  3. In your DNS provider, create a TXT record for SPF using the supplied value.
  4. Create a TXT record for DKIM with the provided selector and public key.
  5. Add an MX record with the selector and value given by the platform.
  6. Add a CNAME record for the tracking URL using the selector and value supplied.
  7. Create a TXT record named _dmarc with the DMARC value provided.
  8. Return to Settings > Email Services > Sending Domain and click Verify Domain.
  9. Confirm that all authentication checks display a Verified status.
  10. Change every email From address in campaigns and automations to the authenticated domain.

07Settings that matter

  • Sending Domain. The place where you add a domain, generate its SPF/DKIM/MX/CNAME/DMARC records, and verify that the DNS entries are correctly published.

08Things to know before you rely on it

  • Only one SPF record is allowed per domain; duplicate records cause failures.
  • SPF can include a maximum of ten DNS lookups; exceeding that limit results in a permerror.
  • Starting DMARC with a "p=reject" policy before SPF and DKIM pass can block legitimate mail; begin with "p=none" for monitoring.
  • Multiple SPF records are not permitted; ensure there is a single SPF entry for the domain.
  • Missing include statements in SPF cause authorized senders to be omitted.
  • Domain alignment must match the From address exactly; subdomain mismatches cause DMARC failures.
  • DNS syntax errors such as extra spaces or quotes break authentication records.

09If something goes wrong

  • Authentication failures continue after setup. Double check each DNS record for syntax errors, duplicate entries, or missing includes and ensure they have fully propagated.
  • Warning signs to avoid. Verify that only one SPF record exists, start DMARC with p=none, include all sending services in SPF, match the From domain exactly, and remove any extra spaces or quotes in DNS entries.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

If your HighLevel emails are bouncing, it’s often because the sending domain hasn’t been authenticated with SPF, DKIM, and DMARC, so providers like Gmail and Outlook reject the messages. Adding the records HighLevel provides and pointing them at your DNS provider gets the process started. Once the records are live, verify them in HighLevel and update all From addresses to use the authenticated domain. That step removes one major cause of rejections, after which you can focus on building reputation.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about email authentication records.

What does "p=none" do in a DMARC record?

"p=none" puts DMARC in monitoring only mode, so failing messages are still delivered but you receive reports about authentication failures.

Can SPF, DKIM, and DMARC be set up on a subdomain instead of the root domain?

Yes. You can publish the records on a subdomain and use that subdomain in the From address, keeping the marketing reputation separate from the primary corporate domain.

Why is a CNAME record required for a tracking URL?

The CNAME makes click and open tracking links appear to come from your own domain, which supports branding and can improve deliverability.

How long should I keep DMARC set to "p=none" before tightening the policy?

Most senders monitor DMARC reports for two to four weeks to confirm all legitimate sources pass authentication before moving to "quarantine" or "reject".

Will fixing SPF, DKIM, and DMARC right away fix all deliverability issues?

It removes a major cause of rejections, but overall deliverability also depends on sender reputation, list quality, and content. Authentication related bounces stop quickly, while broader inbox placement improves over the following weeks.

What happens if my SPF record has more than ten DNS lookups?

Exceeding the ten lookup limit causes a permanent error, causing SPF to fail even if the sending source is authorized. Reduce or flatten includes to stay within the limit.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.