Emails sent through GoHighLevel (GHL) land in spam or show a “via” tag, and your DMARC reports show them failing.
A correct GHL setup publishes an SPF record that includes spf.leadconnectorhq.com (and Mailgun's mailgun.org, which GHL sends through), plus a DKIM public key at the mailo._domainkey selector. The single most common break is an empty or missing mailo._domainkey: GHL signs your outbound mail expecting a key at that selector, so when the public key isn't in your DNS no receiver can verify the signature, DKIM alignment fails, and DMARC quarantines the message. Source: HighLevel Support — Email Authentication Errors · verified 2026-07-18.
dig +short TXT mailo._domainkey.yourdomain.com should return a long k=rsa; p=… value — an empty result is the usual cause.mailo._domainkey if it's missing.spf.leadconnectorhq.com and mailgun.org.p=none + rua to start), then run the free check below to confirm alignment.No. Adding SPF includes and DKIM records (whether TXT or CNAME) only adds authentication — it never blocks mail. The only step that can affect delivery is tightening your DMARC policy to quarantine or reject, and that comes later, once reports confirm every legitimate sender passes.
Yes. Most platforms handle DKIM (and sometimes SPF) so their mail can pass, but the DMARC record is published on your own domain and controlled by you — it's what tells receivers to act on failures. Providers rarely publish it for you, and you want your own rua= address to see the reports.
Send yourself a test message and check the headers for dkim=pass and dmarc=pass — or run the free check below on your domain to see SPF, DKIM and DMARC state, and which sending services currently align, in one place.