
Use this checklist every time you set up a new domain for sending emails through PandaDash / GHL / LeadConnector.
This guide explains what to do if you have just a root domain, and what to do if you are sending from subdomains (like engage.yourdomain.com, reply.yourdomain.com).
Setting up proper email authentication is critical for ensuring your messages reach recipients' inboxes rather than being marked as spam or rejected entirely.
v=spf1 include:_spf.google.com include:mailgun.org include:spf.leadconnectorhq.com ~all
The "@" symbol represents the root domain in DNS configuration. This single record will authorize all the specified services to send email on behalf of your root domain.
v=spf1 include:_spf.google.com include:mailgun.org include:spf.leadconnectorhq.com ~all
Note: The "include" parts in SPF come from your email service providers (like Google, Mailgun, LeadConnector) and are specific to them.
This example shows how to configure the SPF record specifically for the "engage" subdomain. Other subdomains would follow the same pattern with their respective names.
Other steps include DKIM, DMARC, rDNS, and final verification.
Explanation:
DKIM signs your emails with a private key. The receiving mail server checks the matching public key via DNS. This proves the message hasn't been altered in transit and that it's authorized by your domain.
Publish DKIM CNAME or TXT records provided by your email services:
✅ If sending from subdomains (e.g. engage.yourdomain.com), ensure DKIM is configured separately for each subdomain.
✅ Use a tool like MXToolbox DKIM Lookup to verify the record exists and passes.
Explanation:
DMARC is your enforcement policy. It tells Gmail, Outlook, Yahoo, etc. how to treat messages that fail both SPF and DKIM. It also provides visibility via reports so you can watch your domain’s health and impersonation attempts.
Create a TXT record at _dmarc.yourdomain.com with this value to start:
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; ruf=mailto:dmarc@yourdomain.com; fo=1; sp=quarantine; adkim=r; aspf=rYou may optionally create similar DMARC records for each subdomain (e.g. _dmarc.engage.yourdomain.com) if you want subdomain-specific control.
Once you're confident everything is authenticating, you can tighten policy:
v=DMARC1; p=reject; rua=mailto:dmarc@yourdomain.com; ruf=mailto:dmarc@yourdomain.com; fo=1; sp=reject; adkim=s; aspf=sCheck your DMARC results using reports sent to the email addresses in rua and ruf, or use a DMARC monitoring tool like Postmark, Valimail, or GlockApps.
Go to DNS Settings. Advanced Actions -> Export DNS Records.
Manage DNS -> Export Zone File.
Manual copy.
Manual or third-party tool.
Zone Editor -> Export.
Once you have your DNS zone file, upload or paste it into ChatGPT for full review.
Hey ChatGPT, I just finished setting up my domain for email sending. I have uploaded the records for you. Please: 1. Confirm if my SPF, DKIM, and DMARC are structured correctly. 2. Check that I have only one SPF per domain or subdomain. 3. Verify that includes are correct based on Mailgun, LeadConnector, and Google Workspace. 4. Let me know if anything might cause deliverability problems.
After setting up your DNS records, it's smart to simulate a real email send and see how your domain performs.
Two great tools for this:
💡 What You're Looking For:
This confirms your setup is working from all angles—and that your emails are ready for the world.
Email warming tells inbox providers that you're a legitimate sender. It builds trust and reputation gradually, which improves long-term deliverability.
Follow these steps to ensure your domain is properly configured for optimal email deliverability.
Verify SPF, DKIM, and DMARC records are properly configured for your root domain and all subdomains.
Use your provider's export feature to capture a complete snapshot of your current DNS configuration.
Send test emails through Mail-Tester or MailGenius to confirm authentication passes all checks.
Schedule quarterly reviews of your email setup to maintain high deliverability rates.
PandaDash Email Authentication Setup Checklist