1. Domain Acquisition Strategy and Naming Conventions
The foundation of enterprise outbound begins with acquiring brand-adjacent secondary domains. Your secondary domains must look natural, professional, and credible to prospects who inspect the sender address.
If your primary corporate website is solaris.com, acquire variations using reputable prefixes, suffixes, and top-level domains:
- Prefix Variations:
getsolaris.com,trysolaris.com,usesolaris.com,joinsolaris.com. - Suffix Variations:
solarishq.com,solarisapp.com,solarisgroup.co,solarislabs.io. - Trusted Extensions: Stick strictly to .com, .co, and .io. Never purchase budget domains such as .xyz, .online, .site, or .live, because corporate firewalls assign negative heuristic scores to these top-level domains by default.
2. Registrar Selection and DNS Management
Purchase your secondary domains through enterprise-grade registrars with robust API controls and fast DNS propagation. We recommend Cloudflare, Namecheap, or Porkbun. Avoid web hosts that lock DNS editing behind proprietary, slow-updating control panels.
Once registered, point domain nameservers to Cloudflare for centralized DNS management. Cloudflare provides sub-second DNS propagation, free universal SSL certificates, and zero TTL delays when adjusting verification records.
3. Workspace Tenant Provisioning: Google vs Microsoft
Never add secondary cold sending domains as secondary aliases inside your primary company Google Workspace account. Doing so groups your cold mailboxes under the same tenant reputation umbrella as your executive team.
Instead, establish dedicated secondary workspace tenants:
- Separate Admin Account: Create a dedicated Google Workspace or Microsoft 365 organization with its own billing profile.
- Professional User Profiles: Populate each user account with genuine first and last names, real profile headshots, and consistent email signatures. Inboxes without profile photos experience 12% lower open rates on Google Workspace.
- Mailbox Quantity: Create a maximum of 3 user mailboxes per secondary domain. Spreading sending volume across multiple domains is vastly safer than overloading one domain with 10 mailboxes.
4. The Complete DNS Configuration Blueprint
For each secondary domain, enter the following DNS records inside your Cloudflare DNS zone editor:
1. Mail Exchanger (MX) Records
For Google Workspace sending domains, configure the modern single MX record:
Type: MX
Name: @
Server: SMTP.GOOGLE.COM
Priority: 1
TTL: Auto
2. Sender Policy Framework (SPF)
Authorize only Google Workspace servers to transmit email on behalf of this domain:
Type: TXT
Name: @
Value: v=spf1 include:_spf.google.com ~all
TTL: Auto
3. 2048-bit DKIM Key Generation
Inside the Google Admin Console, navigate to Apps > Google Workspace > Gmail > Authenticate email. Select your secondary domain, click Generate new record, choose 2048-bit key length, and set the prefix selector to google. Enter the resulting TXT record into your DNS provider:
Type: TXT
Name: google._domainkey
Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...
TTL: Auto
Return to the Google Admin console and click Start Authentication. Ensure status shows "Authenticating email".
4. DMARC Alignment Record
Add a DMARC policy record to protect your domain from spoofing and satisfy recipient mail server requirements:
Type: TXT
Name: _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@revabove.com; pct=100; sp=none;
TTL: Auto
5. Setting Up Root Domain 301 Redirects
When prospective buyers receive a cold email from momin@tryacme.co, a percentage will type tryacme.co directly into their browser to investigate your company. If that URL returns a blank screen or server error, credibility vanishes.
Inside your Cloudflare dashboard, navigate to Rules > Redirect Rules and configure a permanent 301 redirect:
- Incoming Rule: When incoming hostname equals
tryacme.coorwww.tryacme.co. - Target URL: Redirect with status code 301 to your primary homepage:
https://acme.com/. - Preserve Path: Optional. Directing to the root homepage ensures all traffic lands on your core sales funnel.
6. Post-Configuration Diagnostic Verification
Never assume your DNS records are functional simply because your domain registrar control panel accepted the values. DNS propagation can take between 15 minutes and 24 hours to replicate across global authoritative nameservers.
Before connecting fresh domains to your email sequencer, execute these three diagnostic checks:
- Command-Line Dig Verification: Open your local terminal or command prompt and run direct DNS queries against Google Public DNS (8.8.8.8):
Ensure the output matches your expected Google Workspace or Microsoft 365 values exactly.# Check MX records dig tryacme.co MX +short # Check SPF TXT record dig tryacme.co TXT +short # Check DKIM selector dig google._domainkey.tryacme.co TXT +short - MXToolbox Comprehensive Health Scan: Enter your secondary domain into the MXToolbox SuperTool. Verify that the scan returns green checkmarks across SPF validation, DKIM alignment, and reverse DNS lookup (PTR record).
- Initial Authentication Handshake Test: Send a manual, single test email from your new mailbox to a diagnostic tool like Mail-Tester. Inspect the raw email headers to confirm that SPF, DKIM, and DMARC all report an explicit status of
pass.
7. Common Secondary Domain Setup Mistakes to Avoid
Throughout our technical audits, we observe three frequent configuration blunders that permanently cripple new sending fleets:
- Multiple SPF Records: A domain must have exactly one TXT record beginning with
v=spf1. If you add two separate SPF records (for example, one for Google Workspace and another for a sequencer), mail servers consider the configuration invalid and fail SPF authentication entirely. Merge all authorized servers into a single string. - Missing Custom Tracking CNAME: Using shared tracking domains exposes your outreach to the deliverability penalties of other spammers. Always configure your custom tracking subdomain with SSL enabled.
- Forgetting to Warm Up Forwarding: If you set up root domain redirects, ensure the destination URL resolves cleanly over HTTPS without triggering browser security warnings.
Standards, Official Documentation & References
Primary protocol specifications, regulatory statutes, and internal engineering playbooks cited in this guide:
- IETF RFC 7208: Sender Policy Framework (SPF): Internet Engineering Task Force standard defining the 10-DNS-lookup limit and SPF record evaluation rules.
- Google Workspace Help: Configure SPF Records: Official administrative documentation for publishing TXT Sender Policy Framework records and authorizing outbound Google mail hosts.
- Google Workspace Help: Enable 2048-Bit DKIM Signing: Official guidance for generating cryptographic 2048-bit DomainKeys Identified Mail keys inside Google Workspace Admin.
- Google Workspace Help: Deploy DMARC Policy Records: Administrative guide covering p=none telemetry, p=quarantine enforcement, and RUA aggregate XML reporting.
- IETF RFC 7489: DMARC Specification: Formal specification detailing domain alignment policies and aggregate reporting mechanisms.
- RevAbove 4-Week Infrastructure Deployment Timeline: Internal RevAbove system documentation and implementation reference.
Related Outbound Architecture Playbooks
B2B Cold Email Deliverability Guide
The 10-domain fleet architecture for institutional inbox placement.
Cold Email Warmup: The 21-Day Protocol
How to ramp new mailboxes safely over three weeks.
47 Cold Email Spam Filter Triggers
Technical formatting mistakes that cause server rejections.
Frequently Asked Questions
How long should secondary domains age before sending cold emails?
Secondary domains should age for a minimum of 14 to 21 days while undergoing automated peer-to-peer warmup before sending their first live cold prospecting email.
Can I use domain aliases instead of full workspace accounts?
No. Email aliases share a single SMTP connection and do not have independent sender reputations. You must purchase separate, dedicated user licenses for each sending mailbox.
What happens if a secondary domain gets blacklisted?
Because secondary domains are completely isolated, a blacklisted secondary domain has zero impact on your primary corporate domain or other fleet domains. You simply replace the affected domain with a fresh asset.