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

Conversations and Inbox

How to set up DMARC authentication in HighLevel

In short

DMARC is an email authentication protocol that builds on SPF and DKIM. Adding a DMARC TXT record to your domain tells mailbox providers how to handle messages that fail authentication, reducing spoofing and helping your emails reach the inbox.

AreaEmail · Deliverability
Used forMaintain brand reputation, Achieve compliance for bulk campaigns, Protect the domain from phishing
Setup steps4 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • Email senders who must meet Google and Yahoo authentication requirements.
  • Marketers responsible for ensuring unsubscribe links and keeping spam rates low.

02Email sender requirements, explained

Domain based Message Authentication, Reporting & Conformance (DMARC) adds a policy layer to SPF and DKIM. It lets inbox providers decide whether to deliver, quarantine, or reject messages that fail authentication. HighLevel does not store the DMARC record; it resides in your DNS.

To be compliant, you create a TXT record at the root of your sending domain. The record specifies the DMARC version, a policy (such as p=none), and optional reporting addresses. Google recommends tightening the policy over time after confirming delivery.

The DMARC setting affects every email sent through HighLevel that uses your dedicated sending sub domain. It does not change the content of your messages but influences how providers treat them.

03How businesses use email sender requirements

  • Maintain brand reputation. Add a DMARC record so that recipients see emails that genuinely come from your domain, preventing spoofed messages that could harm trust.
  • Achieve compliance for bulk campaigns. Create the required DMARC TXT entry to satisfy Google and Yahoo sender policies before sending large volumes of email.
  • Protect the domain from phishing. Implement DMARC so inbox providers know how to handle messages that fail SPF or DKIM, reducing the chance of phishing attempts using your domain.

04The numbers and rules that matter

  • February 2024 is the enforcement date for Google and Yahoo requirements.
  • DMARC is required for senders of more than 5,000 emails per day (aggregated across subaccounts using a shared sending domain).
  • Warm up period after enabling a dedicated sending subdomain is 2 to 4 weeks.
  • Spam rate must stay below 0.30%.
  • DMARC TXT record values: Record type TXT, Host _dmarc, Content v=DMARC1; p=none;.
  • One click unsubscribe link is added automatically to the header of every email except 1:1 messages.

05Before you start

  • Senders who transmit more than 5,000 emails per day on a shared sending domain must add a DMARC record.
  • Access to your DNS hosting provider is required to create a TXT record.

06How to set up and use email sender requirements in HighLevel

Add a DMARC TXT record to authenticate your sending domain

  1. Use a free DMARC checker, enter your root domain, and verify whether a DMARC record already exists.
  2. Log in to your DNS hosting provider and start creating a new DNS record.
  3. Set the record type to TXT, the host/name to _dmarc, and the content/value to v=DMARC1; p=none;.
  4. Save the record and use the DMARC checker again to confirm propagation; optionally send a test email and view the header in Gmail.

07What it looks like in HighLevel

08Settings that matter

  • Record type. Specifies the DNS entry format; for DMARC it must be a TXT record.
  • Host / Name. Defines the sub domain for the DMARC policy, always _dmarc.
  • Content / Points to. Contains the DMARC policy string, such as v=DMARC1; p=none;.

09Things to know before you rely on it

  • A DMARC record is required only if you send more than 5,000 emails per day using a shared sending domain.
  • The initial policy in the example is p=none; you should tighten the policy over time according to Google’s recommendations.
  • Propagation of the TXT record may take a few minutes; verification is necessary before assuming compliance.

10If something goes wrong

  • DMARC record does not appear in the checker after saving.. Wait a few minutes, then re run the DMARC checker to confirm propagation. Ensure the host is exactly _dmarc and the record type is TXT.

11How it connects to the rest of HighLevel

Michael's take

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

When your emails get stuck in spam or never arrive, the core issue is often missing authentication or unclear unsubscribe options.

The first thing I get right is the DMARC record. A simple TXT entry that tells inbox providers how to treat failed checks.

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

Common questions

Common questions about email sender requirements.

Do I need DMARC if I already have SPF and DKIM?

Yes. SPF and DKIM authenticate individual messages, while DMARC tells providers how to handle messages that fail those checks.

What volume of email triggers the DMARC requirement?

The requirement applies to senders who transmit more than 5,000 emails per day across subaccounts using a shared sending domain.

How long does the warm up period last after enabling a dedicated sending sub domain?

Plan for a gradual warm up of 2 to 4 weeks, starting with smaller send volumes and increasing gradually.

Can I use a Gmail or Yahoo address as the From address after adding DMARC?

No. Using an @gmail.com or @yahoo.com address as the From address will fail DMARC alignment and likely be blocked.

What happens if my emails do not meet the new requirements?

Non compliant emails may be delayed, routed to spam, or rejected outright by Gmail or Yahoo.

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.