Set up a dedicated GHL sending domain using a subdomain like mail.yourdomain.com or send.yourdomain.com. Configure SPF, DKIM, and DMARC on the subdomain. This isolates your marketing email reputation from your main corporate domain. Add the domain to your ESP first, then configure in GHL's Email Services. Warm up the new domain before sending volume.
GoHighLevel Dedicated Email Domain Setup: Complete Configuration Guide
Why Use a Dedicated Sending Domain
Your sending domain affects everything:
- Reputation isolation — Marketing damage doesn't hurt corporate email (see subdomain strategy)
- DMARC flexibility — Different policies for different domains (authentication guide)
- Clear separation — Transactional vs marketing tracked separately
- Risk management — One domain's blacklisting doesn't affect others
Practitioner note: I've seen agencies tank their main domain's reputation with aggressive marketing, then wonder why their invoices land in spam. Dedicated sending domains prevent this disaster.
Choosing Your Domain Strategy
Option 1: Subdomain (Recommended)
Use a subdomain of your main domain:
| Subdomain | Best For |
|---|---|
| mail.yourdomain.com | General sending |
| marketing.yourdomain.com | Marketing email |
| notify.yourdomain.com | Transactional/notifications |
| news.yourdomain.com | Newsletters |
Advantages:
- Brand recognition maintained
- Inherits some root domain reputation
- Easy to manage
- Looks professional
Option 2: Separate Domain
Use an entirely different domain:
Example: yourbrand.email or yourbrandmail.com
Advantages:
- Complete reputation isolation
- Useful for risky sending
- Fresh start with no history
Disadvantages:
- No brand recognition
- Looks less trustworthy
- More domains to manage
My Recommendation
For most GHL agencies:
Primary corporate: yourdomain.com (personal email, invoices) Marketing: marketing.yourdomain.com (campaigns, newsletters) Transactional: notify.yourdomain.com (confirmations, receipts)
This gives flexibility without complexity.
Step-by-Step Setup
Step 1: Decide on Domain/Subdomain
Choose based on your sending needs:
- Single sending type? Use mail.yourdomain.com
- Separating marketing from transactional? Use two subdomains
- High-risk cold email? Consider a separate domain
Step 2: Configure in Your ESP
Add the domain to your ESP first. In Mailgun:
- Go to Sending > Domains
- Add Domain
- Enter your subdomain (e.g., mail.yourdomain.com)
- Select region
- Copy the required DNS records
In SendGrid:
- Go to Settings > Sender Authentication
- Authenticate Your Domain
- Enter domain details
- Copy DNS records
Step 3: Add DNS Records
Add all required records to your DNS provider.
SPF Record:
mail.yourdomain.com. TXT "v=spf1 include:mailgun.org ~all"
DKIM Records: Usually CNAME or TXT records pointing to your ESP.
DMARC Record:
_dmarc.mail.yourdomain.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]"
Step 4: Verify in ESP
After DNS propagates (usually 5-60 minutes):
- Return to your ESP dashboard
- Click "Verify DNS" or equivalent
- All records should show verified
If verification fails, check for:
- Typos in records
- Missing records
- Conflicting records
Step 5: Configure in GoHighLevel
- Go to Settings > Email Services
- Add new email/domain
- Enter your verified subdomain
- Configure SMTP with your ESP credentials
- Wait for GHL to verify DNS
GHL should show green checkmarks for:
- SPF
- DKIM
- Sending domain
Step 6: Warm Up the Domain
A new domain has zero reputation. Send gradually:
Week 1: 50-100 emails/day Week 2: 200-500 emails/day Week 3: 1,000-2,000 emails/day Week 4: 5,000-10,000 emails/day
Send to engaged contacts first. See our GHL warmup guide for complete schedules.
DNS Configuration Details
SPF Records
Only one SPF record per domain. Combine includes if needed:
v=spf1 include:mailgun.org include:spf.protection.outlook.com ~all
For a subdomain, create a dedicated SPF record:
mail.yourdomain.com. TXT "v=spf1 include:mailgun.org ~all"
DKIM Records
Your ESP provides these. They typically look like:
selector._domainkey.mail.yourdomain.com. TXT "v=DKIM1; k=rsa; p=MIGfMA..."
Or as CNAME:
mg._domainkey.mail.yourdomain.com. CNAME mg._domainkey.mailgun.org
DMARC Records
Start with monitoring mode:
v=DMARC1; p=none; rua=mailto:[email protected]
For subdomain-specific DMARC:
_dmarc.mail.yourdomain.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]"
Note: If your root domain has DMARC with sp= tag, subdomains may inherit that policy.
MX Records (Optional)
If you need to receive email at the sending domain (bounces, replies):
mail.yourdomain.com. MX 10 mxa.mailgun.org.
mail.yourdomain.com. MX 10 mxb.mailgun.org.
Check your ESP's documentation for their MX settings.
Practitioner note: Most agencies forget about reply handling. If customers reply to [email protected], where does it go? Either set up MX records to route to your inbox or use a reply-to address on your main domain.
Multiple Domain Strategy for Agencies
Agencies managing multiple clients need organized domain management.
Per-Client Domains
Each client uses their own sending domain:
- client1.com → marketing.client1.com
- client2.com → mail.client2.com
Advantages: Reputation isolated per client Disadvantages: More DNS management
Shared Agency Domain
All clients send from your agency domain:
- clients.youragency.com
Advantages: Centralized management Disadvantages: Shared reputation, less professional for clients
Hybrid Approach
- White-label clients: Their own domains
- Smaller clients: Shared agency domain
See our agency email management guide for detailed strategies.
Troubleshooting Domain Setup
DNS Records Not Verifying
- Wait for propagation — Can take up to 48 hours
- Check for typos — Copy exactly from ESP
- Check for conflicts — Remove duplicate records
- Use dig or nslookup — Verify records exist
dig mail.yourdomain.com TXT
dig _dmarc.mail.yourdomain.com TXT
SPF Failures
- Too many includes (10 lookup limit)
- Missing ESP include statement
- Record on wrong domain
DKIM Failures
- Wrong selector
- Record too long (needs splitting)
- CNAME vs TXT mismatch
GHL Shows Red X
GHL's verification may lag behind actual DNS. Try:
- Wait 30 minutes
- Remove and re-add domain
- Verify directly with ESP that records pass
Maintaining Your Sending Domain
Regular Monitoring
- Check Google Postmaster Tools weekly
- Monitor bounce rates in ESP
- Review DMARC reports monthly
- Check blacklist status monthly
When Problems Occur
If reputation drops:
- Reduce volume immediately
- Send only to engaged subscribers
- Investigate cause (bad list? content issue?)
- Wait for reputation to recover
Rotating Domains
If a domain is severely damaged:
- Set up a new subdomain
- Warm it up properly
- Gradually shift traffic
- Eventually retire the damaged domain
If you need help setting up a dedicated sending domain or recovering a damaged one, schedule a consultation. I'll configure everything correctly and build a sustainable sending infrastructure.
Sources
- M3AAWG: Best Practices for Subdomain Sending
- Mailgun: Domain Setup Guide
- SendGrid: Domain Authentication
v1.0 · March 2026
Frequently Asked Questions
Should I use a subdomain or separate domain for GoHighLevel email?
Use a subdomain (mail.yourdomain.com) for brand recognition while isolating reputation. A completely separate domain works but looks less professional. Subdomains inherit some reputation from the root but are easier to manage.
How do I set up a dedicated email domain in GoHighLevel?
Add the domain to your ESP (Mailgun, SendGrid) first and complete DNS verification. Then add the same domain in GHL's Email Services. Configure SPF, DKIM, and DMARC records. Verify all show green checkmarks before sending.
Why do I need a separate sending domain for GoHighLevel?
Separating sending domains protects your main domain's reputation. If marketing email damages reputation, your corporate email (invoices, support) continues unaffected. It also allows different policies for different email types.
What's the best subdomain for GoHighLevel email?
Common choices: mail.domain.com, send.domain.com, email.domain.com, or marketing.domain.com. For marketing specifically, use marketing. or promo. to set expectations. For transactional, use mail. or notify.
Do I need to warm up a new GoHighLevel sending domain?
Yes. New domains have no reputation. Start with 50-100 emails/day to engaged recipients and gradually increase over 4-6 weeks. Sending volume too quickly damages the new domain's reputation before it establishes.
Want this handled for you?
Free 30-minute strategy call. Walk away with a plan either way.