Everyone wants to talk about copy, sequences, and AI personalization. Nobody wants to talk about the infrastructure underneath. Domain reputation is the reason your cold emails land in the inbox or vanish into spam — and most companies get it wrong before they send a single campaign.
Here is the blunt version: if you send cold email from a domain with no reputation, your messages go to spam. Not “sometimes.” Not “for some recipients.” Nearly all of them. Google and Microsoft assign reputation scores to sending domains, and a new domain with zero history starts at the bottom. Sending 500 cold emails on day one from that domain is the fastest way to ensure those messages — and every email you send afterward — land in junk.
This is the part of outbound prospecting that nobody wants to deal with. It is not creative. There is no clever hack. It is DNS records, sending schedules, and patience. But it is the single biggest determinant of whether your outbound program generates pipeline or just burns money.
Every outbound program we have audited that was “not working” had one of two problems: targeting was off, or domain infrastructure was broken. The infrastructure problem is more common and more damaging, because it is invisible. You can write the best cold email ever crafted, send it to the perfect prospect, and it will never be read — because it never arrived.
Domain reputation is not a setting you configure once. It is a score that email providers calculate continuously based on your sending behavior, engagement rates, and complaint history. Everything else in outbound — copy, targeting, sequencing — sits on top of it.
Rule number one: never send cold email from your primary domain. Your primary domain is where customer communications, support tickets, invoices, and transactional emails originate. If a spam complaint wave hits your primary domain, your entire business email is compromised. Not just cold outreach — everything.
Secondary domains are variations close enough to your brand that prospects recognize them, but isolated enough that a deliverability problem does not cascade. If your company is acmesoftware.com, your cold sending domains might be acmesoftware.io, getacmesoftware.com, or acme-software.co. Each secondary domain gets its own Google Workspace accounts, its own DNS authentication, and its own warm-up cycle.
Keep them close to your brand — prospects who check the domain should find it plausible. Avoid random strings or domains that look nothing like your company. Common patterns: add “get,” “try,” or “use” as a prefix, or swap the TLD (.io, .co, .dev). Register them through the same registrar as your primary for easier DNS management.
You need 3–5 secondary domains. Not one. If a single domain gets flagged, you retire it and keep sending from the others while a replacement warms up. Treat domains as consumable infrastructure, not permanent assets. Budget $10–15 per domain per year, plus Google Workspace costs for each mailbox.
Every sending domain needs three DNS records configured correctly before a single email goes out. Missing any one of them in 2026 is a near-guarantee that Google and Microsoft will flag your messages.
SPF (Sender Policy Framework) tells receiving servers which mail servers are authorized to send on behalf of your domain. Without it, anyone could spoof your domain, and email providers treat unauthenticated messages as suspicious by default.
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every email, proving the message was not tampered with in transit. It is the digital equivalent of a wax seal — if the signature does not match, the email gets flagged.
DMARC (Domain-based Message Authentication, Reporting & Conformance) ties SPF and DKIM together and tells receiving servers what to do when authentication fails. Start with a “none” policy (monitor only), then move to “quarantine” or “reject” once you are confident your legitimate emails pass checks.
After setting up DNS records, use mail-tester.com to send a test email and get a score out of 10. Anything below 8 means something is misconfigured. MXToolbox and Google Admin Toolbox can diagnose specific SPF/DKIM/DMARC issues. Do this for every domain, every mailbox, before warm-up begins.
A new email account has no sending history. Email providers do not know whether you are a legitimate sender or a spammer. Warm-up is the process of building that trust by gradually increasing volume while maintaining high engagement signals — opens, replies, and low bounce/complaint rates.
Most sending tools (Instantly, Smartlead) have built-in warm-up networks: pools of real inboxes that automatically exchange emails with your accounts, open them, reply to them, and move them out of spam if they land there. This simulates healthy sending behavior and builds the reputation that email providers track.
Weeks 1–2: Warm-up only. No cold emails. Each mailbox sends and receives 10–20 warm-up emails per day. This establishes a baseline of positive engagement.
Weeks 3–4: Begin sending 5–10 cold emails per day per mailbox while warm-up continues in parallel. Monitor bounce rates and spam complaints daily. If bounces exceed 3% or complaints appear, pause cold sending and let warm-up recover the reputation.
Weeks 5–6: Ramp to 20–30 cold emails per day per mailbox. Continue warm-up at a reduced level. By now, your accounts should show consistent inbox placement on monitoring tools.
Week 7+: Full sending capacity at 30–50 cold emails per day per mailbox. Warm-up continues indefinitely at a maintenance level — stopping it abruptly changes your engagement profile and can trigger filters.
The math is straightforward. Each mailbox handles 30–50 cold emails per day. Each domain supports 2–3 mailboxes. You need 3–5 secondary domains. That gives you total daily capacity:
For most mid-market product companies running outbound for the first time, the conservative setup is the right starting point. You are not trying to maximize volume — you are trying to maximize reply rate from a tightly targeted list. Sending 180 highly relevant emails per day to prospects that match your ICP will outperform blasting 750 generic messages every time.
Each mailbox needs its own Google Workspace account ($7/month per user on Business Starter). That means 6–15 Google Workspace seats across your sending domains, or $42–$105/month. Add the domain registration costs and you are looking at $60–$130/month for your entire sending infrastructure. Less than a single team lunch.
Your sending tool (Instantly, Smartlead) should automatically rotate across all mailboxes when sending a campaign. This distributes volume so no single account exceeds safe sending limits. If your tool does not support rotation, you are manually managing risk — and you will eventually get it wrong.
Domain reputation is not a set-and-forget configuration. It shifts based on every email you send, every bounce you receive, and every spam complaint a recipient files. Monitoring is how you catch problems before they cascade.
Google Postmaster Tools is the most important resource. It shows your domain reputation directly from Google’s perspective — classified as High, Medium, Low, or Bad. If your domain drops below Medium, your emails are going to spam for Gmail recipients, which is roughly half of all business email users.
MXToolbox checks whether your domain or IP appears on any major blacklists. Run this weekly. Getting blacklisted is often the first sign that something went wrong — a bad list, a misconfigured record, or a spike in complaints.
Mail-tester.com gives you a deliverability score for individual test emails. Use it after any infrastructure change — new DNS records, new mailboxes, new sending tool connections. It catches configuration mistakes that Postmaster Tools will not surface until they have already damaged your reputation.
Built-in sending tool dashboards (Instantly, Smartlead) track open rates, bounce rates, and reply rates per account. A sudden drop in open rate on a specific mailbox is an early warning that it is hitting spam. Pull it from campaigns immediately and investigate.
Monday: check Google Postmaster for reputation changes. Wednesday: review per-account open and bounce rates in your sending tool. Monthly: run MXToolbox blacklist check on all domains. After any change: mail-tester.com score verification. This takes 15 minutes a week and prevents problems that take months to fix.
A burned domain is one whose reputation has dropped low enough that most emails from it land in spam, regardless of content or targeting. It happens faster than you expect and recovers slower than you want.
Symptoms:
Common causes: sending from a domain that was not fully warmed up, using an unverified list with high bounce rates, sudden volume spikes that trip provider thresholds, or a batch of recipients marking your emails as spam.
Recovery: Stop all cold sending from the burned domain immediately. Keep warm-up running at low volume. If the domain is on a blacklist, submit delisting requests. Wait 2–4 weeks and check Postmaster again. If reputation recovers to Medium or above, resume at very low volume (5–10/day) and ramp slowly. If it stays at Bad after a month, retire the domain and start fresh with a new one.
This is exactly why you run multiple secondary domains. A burned domain is painful but not catastrophic if you have three others still sending. If your entire outbound operation runs through a single domain, one bad week shuts down the entire program.
Prevention is the whole point of this guide. Proper setup, gradual warm-up, verified lists, conservative sending limits, and weekly monitoring. The companies that do this groundwork generate consistent pipeline from outbound. The companies that skip it burn domains, blame the channel, and go back to waiting for inbound.
Domain infrastructure is not where you win at outbound. It is where you avoid losing. The wins come from targeting, messaging, and follow-through — but none of that matters if your emails never reach the inbox. Get this right first. Everything in your outbound prospecting program depends on it.
30-minute discovery call. We’ll map your stack and show you where the margin is hiding.
Schedule Call