Should You Use Your Main Domain for Cold Email?

No. If you're sending cold email at any real volume — say more than 20–30 messages a day, or any automated multi-step sequence — send it from a separate domain that redirects to your main site. Your main domain carries invoices, password resets, contracts, and customer replies. Spam complaints from cold outreach degrade the reputation that all of that mail depends on, and you can't undo it quickly.

The exception is genuinely low-volume, hand-written founder outreach: 10–20 emails a day, one mailbox, high reply rate, no sequencer blasting step 4 to a list of 4,000. That profile rarely generates enough complaints to move the needle. Everything above that line belongs on infrastructure you're willing to burn.

{"placeholder":false}

What you're actually risking

People imagine "getting your domain banned." That's not really how it works. What happens is quieter and harder to reverse:

{"x":1}

• Domain reputation at Gmail and Outlook. Google Postmaster Tools scores reputation per sending domain. Once it drops from High to Low, it takes weeks of clean sending to climb back — and while it's low, your billing emails and support replies land in Promotions or spam too.
• Blocklist entries. Spamhaus DBL and similar lists list *domains*, not just IPs. A DBL listing on yourco.com affects every mailbox on it, and often the links in your emails as well.
• Filter fingerprints on your links. If yourco.com appears in the body of 40,000 cold emails and a chunk get marked as spam, the URL itself becomes a spam signal — including in the emails your support team sends.
• Recipient-side rules. Enterprise mail security tools remember. If a prospect's IT team blocks yourco.com after complaints, your account manager's mail to that company gets blocked too, and nobody tells you.

The asymmetry is what makes this an easy call. A fresh domain costs about $12 a year. Losing inbox placement for your invoices costs a lot more than that.

Does a subdomain protect the root domain?

Partially. Not fully. This is where a lot of advice oversimplifies.

Gmail and Microsoft do evaluate reputation at the sending-domain level, so mail from go.yourco.com is scored somewhat separately from mail from yourco.com. That's why product and lifecycle email is usually sent from a subdomain — it's a real, useful separation.

But the organizational domain still matters. Blocklists frequently list at the registered-domain level. DMARC policy is inherited from the parent unless you publish a separate record. And human recipients — plus the security teams reviewing complaints — see "yourco.com" either way. Reputation systems are increasingly organizational-domain aware, and the trend has been toward *more* correlation, not less.

So: subdomains are the right tool for transactional and marketing mail you control the opt-in for. For cold outreach to people who never asked to hear from you, buy the separate domain.

The lookalike domain playbook

The setup that works is boring and has been stable for years:

{"x":2}

• Register 1–4 variants of your brand. getyourco.com, yourco.io, yourco-hq.com, tryyourco.com. Keep them recognizably yours — a domain that looks nothing like your company reads as phishing to a careful prospect.
• Stick to .com, .co, .io, or your country TLD. Cheap TLDs like .top, .click, .buzz, and .xyz carry measurably worse baseline reputation because that's where bulk spammers shop. Saving $8 isn't worth it.
• Set up a real 301 redirect to your main site. A parked domain with a registrar placeholder page is a red flag when someone checks. Redirect the root to yourco.com and be done.
• Publish full authentication on every domain. SPF, DKIM, and a DMARC record — start at p=none while you confirm alignment, then move to quarantine. Our SPF, DKIM, and DMARC setup guide walks through the exact records.
• Create 2–3 mailboxes per domain, not eight. Domains hosting a dozen sending mailboxes look like disposable infrastructure, because usually they are.
• Warm each mailbox for 2–4 weeks before real sends, and keep warm-up running underneath live campaigns. See how long to warm up an email account for the ramp schedule.
• Cap at 20–40 emails per mailbox per day once warm. More than that on a fresh domain is where problems start.

Do the volume math before you buy anything

Work backwards from your target. Say you want 3,000 cold emails a month — that's roughly 150 a day across 20 working days.

At 30 emails per mailbox per day, that's 5 mailboxes. At 2–3 mailboxes per domain, that's 2 domains. Cost: about $25/year in domains, plus mailbox hosting at roughly $6–8 per user per month for Google Workspace or Microsoft 365 Business Basic — call it $35–40/month all-in for the sending infrastructure.

Now compare that to the version where you push 150 a day through your main domain to save $40. There isn't a serious argument for it.

One caveat on ramping: those numbers assume warmed mailboxes. In week one you're sending 5–10 a day per mailbox, not 30. Plan the domain purchase 4–6 weeks before you need the pipeline, not the week your quarter starts.

When the main domain is genuinely fine

There are real cases where a separate domain is overkill:

{"x":3}

• Founder-led sales at 10–20 emails a day. Hand-written, researched, one mailbox, replies coming back at 8–15%. You are not generating complaint volume.
• Warm and semi-warm audiences. Event attendees, trial signups who went dark, past customers, inbound leads you never called. These aren't cold in the filtering sense — but they still need one-click unsubscribe and a suppression list.
• Regulated or enterprise sales where domain identity matters. If your prospect's procurement team will look you up before replying, mail from tryyourco-sales.io is a liability, not an asset. Send from the real domain and keep volume low.
• Recruiting and partnership outreach. Usually low volume, usually high relevance, usually better received from the actual company domain.

The dividing line isn't cold vs. warm. It's complaint volume. If you can't answer "how many spam complaints per thousand am I generating," assume it's higher than you think and use a separate domain.

Five mistakes that undo the whole setup

{"x":4}

• Sending on day one. A domain registered yesterday with no sending history is one of the strongest spam signals there is. Let it sit 2–4 weeks minimum while warm-up runs.
• Skipping DMARC on the new domain. Filters increasingly treat missing DMARC as a negative signal, and unauthenticated bulk mail to Gmail and Yahoo consumer addresses is now effectively blocked outright.
• Reusing one domain across all clients. Agencies: one sending domain per client, always. A single client's bad list shouldn't take down every campaign you run.
• No monitoring per domain. Add each sending domain to Google Postmaster Tools separately. Reputation problems show up there days before they show up in your reply rate.
• Assuming the domain fixes the list. A pristine domain sending to a scraped list with 12% bounces will burn just as fast. Verify, suppress, and keep bounce rate under 2–3%.

How Sendvanta fits

Sendvanta sends through your own mailboxes — Gmail, Microsoft 365, or SMTP/IMAP — so your sending domains stay yours and nothing routes through shared IPs. On paid plans you can register a sending domain in-app for a one-time $20 and add managed mailboxes at $4/mo each if you'd rather not set them up manually; connecting mailboxes you already own is free on every plan, including the free tier.

The part that matters for domain separation is the health scoring. Sendvanta scores deliverability risk in layers — mailbox, domain, DKIM, and IP — so if one sending domain starts degrading, it slows or pauses that domain instead of letting the damage spread across the account. Warm-up runs with real labeled messages inside the workspace, drafts get SpamAssassin-scored before send, and seed mailboxes test actual inbox placement per domain.

The free plan is $0 forever with 1,000 active leads, 3,000 emails a month, and up to 10 of your own SMTP mailboxes — enough to run the two-domain, five-mailbox setup described above and see what your placement actually looks like. Paid plans start at $29/mo.

Methodology: this guide reflects domain, authentication, and sender-requirement practices as of February 2026, based on published Gmail and Microsoft bulk sender requirements, Spamhaus listing policy, and observed sending patterns across Sendvanta workspaces.