How to Add a Dedicated Sending Domain in GoHighLevel

A GoHighLevel custom email domain is a dedicated subdomain you authenticate inside your account so outbound email comes from your own brand instead of a shared sending address. HighLevel's support documentation sets this up under Settings, not under a separate app.

The whole process runs on DNS records rather than code.

The path is Settings > Email Services > the "Dedicated Domain and IP" tab > Add Domain. HighLevel recommends entering a subdomain of your root domain, something like mail.agency123.com or no-reply.agency123.com, rather than the bare root domain itself.

That separation matters. A subdomain can carry its own sending reputation without touching the MX records your root domain already uses for Google Workspace or another inbox provider.

Setting Up a GoHighLevel Custom Email Domain

Once the subdomain is added, GoHighLevel generates the records needed to prove you own it and that mail sent under its name is legitimate. The setup follows a fixed sequence:

• Add the subdomain in the Dedicated Domain and IP tab.
• Open the DNS records screen HighLevel generates for that subdomain.
• Copy each record's Type, Name/Host and Value into your DNS provider's dashboard, entering only the prefix HighLevel shows rather than the full domain string.
• Return to HighLevel and verify. Propagation can take anywhere from a few minutes on Cloudflare or SiteGround to as long as 48 hours on GoDaddy or Namecheap.

HighLevel's manual-records article is specific about one failure mode. Pasting the full subdomain into the Name/Host field instead of just the prefix causes duplication and a failed verification. If the system shows "replies.companyname.com," the field only wants "replies."

The DNS Records Involved

Five records in total get added. They split across three jobs: proving ownership, authenticating sends, and routing mail flow.

The MX records pointing at Mailgun's servers are the tell that GoHighLevel's LC Email runs on Mailgun's infrastructure underneath.

Only one SPF and one DKIM record per domain are supported, so any leftover SPF or MX entries already sitting on that subdomain need to come out first or verification will fail silently.

What a Dedicated Domain Unlocks

Dedicated sending domains aren't available to every plan tier. The feature is limited to LC Email users, and a single account can register multiple sending domains, with up to five specifically for calendar-related emails.

Once a domain is verified, the Reply & Forward Settings panel adds forwarding addresses, reply routing, and BCC copies, but only for Mailgun and LC Email domains. Custom SMTP providers don't get those options.

That gap is worth planning around before launch rather than after. An agency that sets up a GHL account on custom SMTP and later wants reply tracking back into the Conversations tab will need to migrate to LC Email or Mailgun first, which means re-running this same DNS process.

Agencies running white-label support across multiple client subaccounts often standardize on dedicated domains from day one for exactly this reason. Swapping sending infrastructure after a client's automations are already live from a shared address is far more disruptive than configuring it correctly at setup.

The DNS work is identical to what the GoHighLevel white label domain setup requires, just scoped to email instead of the funnel domain. Get it right once, and every automated email the account sends afterward inherits that domain's reputation instead of a shared one.

Cover photo by Miguel Á. Padriñán on Pexels