Should you send cold email from your main domain?
It depends on how you send. If you write each email yourself, a handful a day, to people you researched and addresses you verified, your main domain is a defensible choice. Once you add a sequencer, a database list or a second sender, move cold email to a separate domain that looks like your brand.
The reason is how mailbox providers keep score. Google's email sender guidelines say Gmail tracks volume, feedback and limits per domain and IP address, and that over time, user spam reports can lower your domain's reputation. Your main domain carries everything else your company sends: replies to customers, invoices, password resets, hiring emails. In our judgement, cold email is the mail most likely to be reported, so the question is whether you can afford to put that score at risk.
The same guidelines also tell senders not to email people who didn't sign up to hear from them, and warn that those recipients might mark the messages as spam. Every cold email sits on the wrong side of that line, whichever domain it comes from. A secondary domain changes where the damage lands. It does nothing to reduce the chance of a report.
What is at risk on your main domain?
Three things are at risk: inbox placement for all your company's mail, your sending allowance, and time. Google's guidelines list what moves them:
- Spam reports. Google's sender FAQ says spam rate is calculated daily and should stay below 0.1%, never reaching 0.3%. At small volumes one report moves that rate a lot: one report among 45 messages to personal Gmail in a day is about 2.2%, by our arithmetic.
- Sudden volume. The guidelines warn that immediately doubling your usual volume could result in rate limiting or reputation drops. A founder whose domain normally sends 30 emails a day and adds 30 cold ones has doubled it, though Google's example is aimed at senders without a history of large volumes and gives no threshold.
- Bounces. Google advises reducing volume when messages start bouncing or being deferred, then increasing slowly again. Unverified lists bounce.
Google's published thresholds come with a caveat: the FAQ says its sender requirements apply only to mail sent to personal Gmail accounts, not to Google Workspace recipients. Many B2B prospects use work mailboxes, so treat these numbers as a guide, not a tested limit for cold email.
What a bad week looks like is described in one r/Emailmarketing thread from May 2026 (nearly 60 comments in the Reddit archive when checked on 24 October 2026). A team sent a 200,000-email Mailchimp campaign to its marketing list in two weekly halves from what they called a subdomain (commenters pointed out that their example, emailboxout.com, is a separate domain). Afterwards, routine replies from their main domain started landing in Gmail spam. Commenters disagreed about the cause, from no warm-up to the way the domains were linked, and the thread shows no confirmed fix. It is one team's report, and it shows that splitting domains is no guarantee on its own.
Is a subdomain or alias domain enough separation?
Not fully. A subdomain such as outreach.yourco.com shares more with your main domain than most setup guides admit:
- Google counts them together. The sender FAQ says that when it calculates the 5,000-a-day bulk-sender line, it counts all messages from the same primary domain. Its example adds 2,500 messages from solarmora.com to 2,500 from promotions.solarmora.com and treats the sender as one bulk sender.
- DMARC policy is inherited. Under RFC 7489, the DMARC standard, a subdomain with no DMARC record of its own follows the main domain's policy, unless the main domain's record sets a separate subdomain policy with the sp tag.
- Aliases share your account. Google Workspace lets you add a user alias domain that gives every user a second address at another domain. Workspace's sending limits page says messages sent from an alias count toward the same user's limit, which is 2,000 messages a day, or 500 on a trial account.
Neither Google's guidelines nor its FAQ says how far a subdomain's reputation spills onto its parent. Commenters in the thread above argued both ways, and none cited Google. What the documents do show is that a subdomain is linked to the main domain in counting and in policy. A separate registered domain, with its own mailboxes, is the only setup that keeps the two apart on paper.
What does a secondary domain cost?
Less than most people expect in money, more in time. Here is the setup for one separate domain with one mailbox, as of 24 October 2026:
| Item | Cost or time |
|---|---|
| .com domain | $11.08 a year at Porkbun |
| Mailbox | One Google Workspace licence, priced per user per month on Google's pricing page (shown in your local currency) |
| Authentication | SPF or DKIM for every sender; SPF, DKIM and DMARC once you send close to 5,000 a day to personal Gmail |
| Warm-up | Low, steady volume at first; Google gives no fixed warm-up period |
| Trial limits | 500 messages a day on a Workspace trial; after you convert, limits rise once the domain has paid a cumulative $100, and the increase can take up to 75 days |
The trial row catches people out. If you start a new Workspace account for the secondary domain on a free trial, the sending limits page says limits aren't increased during the trial; after you convert, they rise once that domain has paid a cumulative $100, and the increase can take up to 75 days to arrive. Check how you'll set up the mailbox before you plan your first send date.
Now the worked example. In one r/coldemail thread from March 2026 (about 15 comments when checked on 24 October 2026), a web developer planned to send about 10 emails a week and asked whether that needed a new domain. One reply advised buying 10 to 20 domains with 2 mailboxes each. That is 20 to 40 mailboxes for 10 emails a week, or one email per mailbox every two to four weeks, plus 20 to 40 licences to pay for each month. One domain and one mailbox covers that volume many times over; in our view, multi-domain setups suit agencies sending thousands a day. Our guide to how long to warm up a new domain covers the waiting period.
Main domain, subdomain or separate domain: which should you pick?
Pick by what you would lose and how you send, not by what an outreach vendor sells. This table is our judgement, built on Google's documents above:
| Your situation | What we'd pick | Why |
|---|---|---|
| You write each email yourself, a few a day, to researched people at verified addresses | Main domain | Replies land in the inbox you already watch, and the volume looks like normal business mail |
| Your main domain sends invoices, support or product mail that customers rely on | Separate domain, even at low volume | One bad week would hit mail your customers need |
| You use a sequencer, a database list or more than one sender | Separate domain, one or two mailboxes | Volume, bounces and reports rise together |
| You want separation but only have a subdomain | Treat it as your main domain | Google counts subdomain mail with the primary domain for its bulk-sender line, and a subdomain without its own DMARC record inherits the main domain's policy |
| You want to start a campaign this week | Main domain at low volume, or wait | A brand-new domain has no sending history yet |
The r/coldemail thread above is a fair picture of the advice you'll get. By our count, nine replies pushed a separate domain and three said low manual volume was probably fine for now, though one of those three still recommended a sister domain. At least three of the nine came from people who said they run an outreach agency or build outreach tools. One agency reply put the case this way: "the risk isn't about volume, it's about what happens if even one or two recipients hit 'report spam.'" That is a fair point about ratios at low volume, and it is one commenter's view.
How do you protect whichever domain you send from?
The same habits protect either domain:
- Authenticate first. Google asks every sender to set up SPF or DKIM, and bulk senders to add DMARC.
- Verify every address. Google's guidelines tell senders to reduce volume when messages start bouncing, then increase slowly again, so every bounce you avoid keeps a new domain on schedule.
- Keep volume steady. Google advises sending at a consistent rate and avoiding bursts.
- Write to fewer, better-fit people. In our judgement, a person with a clear reason to hear from you is less likely to report you.
- Skip the tracking pixel. Our guide to whether open tracking hurts deliverability explains the trade-off.
- Watch the signs. If replies from your main domain start landing in spam, stop cold sends first and read our guide to fixing cold emails that go to spam.
If you send from Google Workspace, our guide to sending cold email from Gmail covers the account limits in detail. Siela's AI SDR follows the same habits by default: it finds and verifies each person's work email, emails only deliverable addresses, and sends up to 150 a day per Gmail mailbox, 2 to 5 minutes apart.
Frequently asked questions
Does a subdomain protect your main domain from cold email?
Only partly. Google's sender FAQ counts mail from a subdomain together with the primary domain when it decides who is a bulk sender, and under the DMARC standard a subdomain without its own DMARC record inherits the main domain's policy unless a separate subdomain policy is set. Google doesn't publish how much reputation carries between them, so treat a subdomain as part of your main domain.
How many secondary domains does a founder need for cold email?
Usually one, with one or two mailboxes. In our view, multi-domain setups with dozens of mailboxes suit agencies sending thousands of emails a day. At ten emails a week, twenty domains with two mailboxes each would mean one email per mailbox every two to four weeks, with a licence to pay for each one every month.
Can you use a Google Workspace alias domain for cold email?
You can send from one, but it only partly separates your mail. A user alias domain gives each user a second address on the same account, and Google's sending limits page says messages from an alias count toward that user's daily limit of 2,000 messages, or 500 on a trial account. Cold sends and everyday mail then share one mailbox and one limit.
Should replies to a secondary domain move to your main address?
You can keep the conversation on the secondary domain until the prospect is clearly interested, then introduce your main address. Google's guidelines note that messages from an address in the recipient's contacts are less likely to be marked as spam, so a prospect who has replied and saved your main address is a lower-risk recipient than a cold one.
What should the secondary domain's website show?
Point it at your main website so a prospect who checks the domain lands on your real company. In our view, a lookalike domain with no site, or a parked page, makes a careful reader suspicious. Keep the brand name recognisable, for example getyourco.com or yourco-mail.com, and use the same name and signature as on your main domain.
Sources
- Google Workspace Admin Help: Email sender guidelines (checked 24 Oct 2026)
- Google Workspace Admin Help: Email sender guidelines FAQ (checked 24 Oct 2026)
- Google Workspace: Gmail sending limits in Google Workspace (checked 24 Oct 2026)
- Google Workspace Admin Help: FAQ for multiple domains (checked 24 Oct 2026)
- RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC) (March 2015)
- Porkbun: .com domain pricing (checked 24 Oct 2026)
- Google Workspace: Pricing (checked 24 Oct 2026)
- r/coldemail: Secondary domain needed? (19 Mar 2026)
- r/Emailmarketing: Gmail is flagging our main domain as spam even though we send campaigns from a subdomain via mailchimp (2 May 2026)