A sending domain is the custom web domain you use to send marketing emails, establishing your brand identity and building inbox reputation.
What Is a Sending Domain?
A sending domain is the specific domain name used in your "From" email address when delivering marketing and transactional emails under your business identity.
Think of your sending domain as your store’s official business address and letterhead. Rather than sending emails from a generic @gmail.com or @yahoo.com address, a custom sending domain (such as @yourstore.com) proves to receiving inbox providers that the message actually originated from your verified brand.
Why a Sending Domain Matters
Email marketing success depends on your domain’s reputation with inbox providers like Gmail, Yahoo, and Outlook. Without a verified sending domain, inbox algorithms view your emails with suspicion, often routing them directly to the spam folder.
Major inbox providers now enforce strict authentication mandates. Sending bulk marketing emails from free webmail accounts damages customer trust, lowers open rates, and violates modern deliverability compliance rules.
How Sending Domains Work
1. You register a custom business domain (e.g., yourstore.com) or dedicated subdomain (e.g., mail.yourstore.com)
2. DNS authentication records (SPF, DKIM, and DMARC) are configured for your domain
3. Receiving mail servers query these DNS records to verify message authenticity
4. Consistent engagement from subscribers builds a positive sending reputation tied directly to your domain
Root Domain vs Subdomain, Explained
| Domain Type | Description | Best Use Case |
|---|---|---|
Root Domain (yourstore.com) | Primary web address used for main website and business emails | Corporate email and direct customer communications |
Subdomain (mail.yourstore.com) | Dedicated prefix created specifically for email delivery | Bulk marketing campaigns, newsletters, and automated flows |
Shared Domain (adflipr-mail.com) | Default domain shared across starter accounts | Initial account setup and testing |
Using a dedicated subdomain for marketing campaigns isolates your primary domain reputation, protecting your business email deliverability.
A Real Sending Domain DNS Record
Host: mail.yourstore.com
Type: CNAME
Value: send.adflipr-dns.com
Host: The subdomain prefix used for marketing email routing.
CNAME Value: Connects your domain directly to Adflipr’s high-reputation sending infrastructure.
How to Set It Up in Adflipr
1. Navigate to Settings > Sending Domains in your Adflipr dashboard
2. Enter your custom domain or preferred marketing subdomain (e.g., mail.yourstore.com)
3. Copy the generated DNS records (CNAME, SPF, and DKIM)
4. Add the records to your domain DNS provider (Cloudflare, GoDaddy, Namecheap, etc.)
5. Click Verify Records in Adflipr to confirm your domain authentication is live
Best Practices
— Always use a dedicated subdomain (e.g., mail.yourstore.com) for promotional campaigns
— Verify SPF, DKIM, and DMARC records before launching bulk broadcasts
— Maintain consistent sending volume to build a steady domain reputation
— Monitor bounce rates and spam complaints closely in Adflipr analytics
Common Mistakes
— Sending bulk marketing campaigns from free webmail addresses (@gmail.com, @yahoo.com)
— Frequently changing domain names, which resets your established sending reputation
— Forgetting to update DNS records after transferring domain registrars
— Sending unauthenticated emails from multiple uncoordinated marketing platforms
Frequently Asked Questions
No. Gmail and Yahoo enforce strict DMARC policies that spam-box or block bulk emails sent from free webmail addresses through third-party platforms. You must use a custom sending domain.
Using a dedicated subdomain (e.g., mail.yourstore.com) is strongly recommended. It isolates your marketing deliverability reputation from your corporate email and root domain operations.
Building a strong domain reputation typically takes 2 to 4 weeks of consistent warm-up sending to engaged subscribers.
Yes. Transferring your DNS host will wipe custom records unless you re-enter your SPF, DKIM, and CNAME authentication records with your new registrar.
