Home/HighLevel/Troubleshooting/SPF, DKIM, DMARC
Troubleshooting · Email
Fix: GoHighLevel SPF, DKIM or DMARC failing. Records and alignment.
Authentication fails on record details or on alignment. SPF also has a lookup limit, so too many includes break it.
The short answer
SPF, DKIM or DMARC fail in GoHighLevel when record values are wrong, SPF has too many includes and exceeds its lookup limit, DMARC alignment fails because the authenticated domain differs from the From domain, or records sit at the wrong DNS host.
Michael is a sponsored HighLevel affiliate. Links to HighLevel use his partner link at no extra cost to you. HighLevel prices and product facts on this page come from HighLevel's own pricing page and help center, checked on the date above.
Causes
Why is SPF, DKIM or DMARC failing in HighLevel?
Most cases come down to the four causes in this table. Check each one before you change anything.
| Cause | How to check |
|---|---|
| Wrong values | Compare records with HighLevel |
| Too many SPF includes | Count includes |
| DMARC alignment | From domain vs authenticated domain |
| Wrong DNS host | Nameserver location |
Diagnose
How do you confirm which record is failing before you edit DNS?
There are two different kinds of failing, and they have different fixes. Either HighLevel will not verify the records, or the records verify but real emails still fail the checks. Find out which one you have.
For the first, go to Settings, Email Services, Dedicated Domain and IP and look at which record shows unverified. Then run a public DNS lookup on that exact host. A missing or wrong result is a DNS problem, and fix DNS records not verifying covers host names and conflicts. While you are there, count the SPF records on the domain. There should be one.
For the second, send a test to your own Gmail address and open the original message. It shows a pass or fail for SPF, DKIM and DMARC separately. If SPF and DKIM pass but DMARC fails, the issue is alignment: the From address is on a different domain from the one you authenticated. If SPF fails on its own, count the includes in the record, since too many pushes it over the lookup limit. Check for an existing DMARC record before you add another on the host _dmarc.
Fix
Fix it step by step.
- Compare each record with what HighLevel shows.
- Consolidate SPF includes to stay under the lookup limit.
- Send from an address on the authenticated domain.
- Add a DMARC record with host _dmarc if missing.
- Click Verify Records again.
Still stuck
When to contact support.
If none of these fix it, open Help and Support from the question mark at the top right of your agency view, then start a chat (AI Support Chat or Agent Chat), join a Zoom call or open a ticket. Have your Agency Relationship Number and the Location ID of the subaccount ready, add screenshots of the problem, and turn on Support Access so the team can look inside the account. Only Agency Admins and Agency Users can reach HighLevel support; subaccount users go through their agency.
- Use one SPF record per domain
If records verify, alignment is right and a real inbox still shows a fail, send support the sending domain, a screenshot of the record status, the DNS records as published and the full headers of one failing email.
For prevention, keep one SPF record per domain, send only from addresses on the authenticated domain and retest in a real inbox after every DNS change. The full setup is in set up SPF, DKIM and DMARC. After records pass, warm up the domain, and if mail still lands in junk see fix emails going to spam. For short answers on this topic, see GoHighLevel email answers.
If you want a clean account to test the fix in, the 30 day GoHighLevel trial through Michael's link gives you one. Agencies that want the top plan can read about the Founder Plan.

One SPF record, aligned From address, then DMARC passes.
Questions
Common questions.
Why is SPF, DKIM or DMARC failing?
SPF, DKIM or DMARC fail when record values are wrong, SPF has too many includes and exceeds its lookup limit, DMARC alignment fails because the authenticated domain differs from the From domain, or records sit at the wrong DNS host.
How do I prevent it?
Keep one SPF record per domain, send only from addresses on the authenticated domain and retest in a real inbox after every DNS change.
When should I contact HighLevel support?
Contact support once you have checked every cause on this page and it still fails, or when the fix sits on HighLevel's side. If records verify, alignment is right and a real inbox still shows a fail, send support the sending domain, a screenshot of the record status, the DNS records as published and the full headers of one failing email.
What DMARC record should I start with?
A safe starting value is v=DMARC1; p=none; added as a TXT record on the host _dmarc. Check first that the domain does not already have a DMARC record.
Why does DMARC fail when SPF and DKIM pass?
DMARC also checks alignment. The SPF or DKIM domain must match the domain in the From address. Send from an address on the domain you authenticated.
Can I have two SPF records on one domain?
No. Use one SPF record per domain and combine the senders inside it. Consolidate includes so you stay under the lookup limit.
Next step
See it in your own account. Thirty days, every feature.
Start a 30 day trial through Michael's link, build the first system and test it before the first invoice. Usage fees for phone, SMS, email and AI can apply during the trial.
HighLevel has three plans at a flat monthly price, each with unlimited users and contacts. See what each one includes and what it costs.
Compare the PlansStarter, Unlimited and Founder