Published March 21, 2026 · Last updated March 21, 2026
GoHighLevel domain verification fails on GoDaddy when the DNS records on your sending subdomain don't match what Mailgun expects. The most common cause is GoDaddy's DNS interface automatically appending your root domain to record names — so a DKIM record intended for pic._domainkey.mg.yourdomain.com ends up pointing to pic._domainkey.mg.yourdomain.com.yourdomain.com.
Mailgun requires five types of DNS records on your sending subdomain (e.g., mg.yourdomain.com) for full verification:
include:mailgun.org.mxa.mailgun.org and mxb.mailgun.org on your sending subdomain.email.mg.yourdomain.com.When adding DNS records in GoDaddy, the "Host" field should contain only the subdomain portion — not the full hostname. For example:
mg.yourdomain.com, enter mg as the Host, not mg.yourdomain.com.pic._domainkey.mg.yourdomain.com, enter pic._domainkey.mg as the Host.mg as the Host.GoDaddy automatically appends your root domain to whatever you enter in the Host field. If you enter the full hostname, it gets doubled.
FixMySender scans your current DNS records, identifies exactly which records are missing or misconfigured, and generates the correct values pre-formatted for GoDaddy's DNS interface. You get copy-paste-ready Host and Value fields — no guesswork about what GoDaddy will append.
After the records are applied, FixMySender confirms DNS propagation and verifies the domain inside GoHighLevel/Mailgun, providing verification proof and an implementation summary.
Need help with your domain verification?
Get Verified Now