Home · Email authentication by platform · Updated 18 November 2026

HighLevel SPF, DKIM and DMARC setup (dedicated sending domain)

Short answer: In HighLevel go to Settings → Email Services → Dedicated Domain and IP → Add Domain, enter a subdomain (HighLevel’s example is lc.mydomain.com), add the records HighLevel shows, then click Verify Records and set your From name and email. Add a DMARC TXT record at _dmarc; HighLevel’s troubleshooting guide says to start with v=DMARC1; p=none;.

Ad CourseSignal is run by Urban Huntsman Ltd, an independent HighLevel affiliate and also a HighLevel agency. We earn a commission if you sign up through our HighLevel link (#Ad), 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.

By default, HighLevel’s LC Email sends from shared infrastructure and shows HighLevel’s servers in “sent via” headers. A dedicated sending domain sends as your brand (HighLevel: Dedicated email sending domains). HighLevel’s best-practice guide lists it as its first recommendation and says custom SMTP users do not have this option.

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. HighLevel shows the DKIM selector with the DKIM record, so enter that selector in the checker. Then run the email blacklist checker on the same domain. Both run free with no sign-up.

Records you will add

HighLevel generates the records for your subdomain. Its troubleshooting guide lists these record types; copy each value from the HighLevel screen.

PurposeTypeName / hostValue
SPFTXTAs HighLevel showsCopy from your HighLevel dashboard. HighLevel’s guide says it typically includes include:spf.leadconnectorhq.com include:mailgun.org
DKIMTXTThe DKIM selector HighLevel providesCopy from your HighLevel dashboard (the public key)
MXMXAs HighLevel showsCopy from your HighLevel dashboard
TrackingCNAMEAs HighLevel showsCopy from your HighLevel dashboard
DMARCTXT_dmarcStart with v=DMARC1; p=none; (HighLevel troubleshooting guide)

Record list from HighLevel: Email authentication errors. HighLevel says multiple DKIM records for the same domain are not supported, and propagation can take up to 24 hours.

Step by step in HighLevel

  1. Go to Settings → Email Services and click the Dedicated Domain and IP tab.
  2. Click Add Domain, enter your subdomain (for example lc.mydomain.com) and click Add & Verify.
  3. HighLevel can auto-configure the records. If that is not available, add each record manually at your DNS provider using the values HighLevel shows.
  4. Click Verify Records once the updates are complete.
  5. Click the three-dot menu → Set Headers, enter your From Name and From Email, and click Save.
  6. Add your DMARC record (next section) if the domain does not already have one.

DMARC

HighLevel says that from February 2024 Gmail and Yahoo require DKIM and DMARC, and strongly recommends both (HighLevel: Email authentication, DMARC). The simplest valid record is a TXT record named _dmarc with v=DMARC1; p=none;.

HighLevel’s two guides show different starting policies. The troubleshooting guide says to start with v=DMARC1; p=none; and lists “policy set to reject without proper SPF/DKIM setup” as a failure cause. The best-practice guide’s example uses v=DMARC1; p=reject (HighLevel: Email sending guide). If you are not sure every service that sends as your domain passes SPF or DKIM, starting at p=none and reading reports is the lower-risk route.

Keep one DMARC record per domain. If one exists, edit it rather than adding another.

Things HighLevel 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 HighLevel yet?

HighLevel’s pricing page lists a 14-day free trial on every plan. If you start one, set up the dedicated sending domain above before you send to your list.

HighLevel’s pricing page lists a 14-day free trial on every plan. Billing starts automatically when the trial ends unless you cancel, and usage charges (phone, SMS, email, some AI) can apply during the trial. Checked 18 November 2026 (GMT).

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

Where is the dedicated sending domain setting in HighLevel?

Settings → Email Services → Dedicated Domain and IP → Add Domain.

Should I use my root domain or a subdomain in HighLevel?

HighLevel recommends a subdomain (for example lc.mydomain.com) to protect your root domain’s reputation. Your From address can still use the root domain.

What DMARC record should I use with HighLevel?

HighLevel’s troubleshooting guide says to start with v=DMARC1; p=none; at the name _dmarc and tighten later. Its best-practice guide shows p=reject as an example.

Why does HighLevel say my domain has pre-existing records?

The subdomain already has MX or SPF records for another service, or your domain has a wildcard record. Use a fresh subdomain or remove the wildcard temporarily while you verify.

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.