When outbound email performance drops, the temptation is to reach for a fresh domain. It feels like a reset button. But as one practitioner recently pointed out, this is the equivalent of a fruit seller who never inspects his produce, only moves to the next town when complaints start. The problem follows him because he never changed the fruit. If you want to read the original framing, see the original LinkedIn post.

In outbound email, the fruit is your contact list and the way you manage it. The town is your sending domain. Changing the town without changing the fruit means mailbox providers will eventually recognise your cart again, no matter what name is painted on the side.

The domain rotation trap

Rotating domains is a common tactic when inbox placement falls. The logic seems sound: a new domain has no reputation, so it starts with a clean slate. In practice, mailbox providers evaluate far more than the domain. They look at sending patterns, recipient engagement, authentication, complaint rates, and the quality of the addresses you send to. A new domain that sends to the same problematic list will quickly develop the same reputation problems.

Worse, domain rotation can actively harm you. If you abandon a domain and start fresh repeatedly, you never build the sending history that mailbox providers use to trust legitimate senders. You also risk your brand being associated with a pattern of disposable infrastructure, which is exactly the kind of behaviour that filters are designed to catch.

What mailbox providers actually see

Mailbox providers do not see a domain in isolation. They see a sender. That sender has a fingerprint made up of:

  • The domains and IPs you send from
  • Your authentication setup (SPF, DKIM, DMARC)
  • The volume and consistency of your sending
  • How recipients interact with your mail (opens, replies, complaints)
  • The quality of your address list, including spam traps and invalid addresses

When you switch domains but keep the same list hygiene practices, you are changing one variable in a system that evaluates many. The underlying signals that caused the reputation drop remain.

The real problem: no record of where contacts came from

One of the most overlooked issues in outbound email is contact provenance. Many teams import addresses from multiple sources without tracking where each contact came from, when they were added, or what consent basis exists. This creates several problems:

  1. You cannot tell which sources produce good engagement and which produce complaints.
  2. You cannot remove entire sources that turn out to be low quality.
  3. You have no way to know if a contact has already opted out or bounced in a previous campaign.

Without provenance, every import is a gamble. You are filling your cart from any orchard that will sell to you, and you have no idea what is inside the fruit.

Validation is not a safe list

Running an address through a validation tool is not the same as having a safe list. Validation checks whether an address is syntactically correct and whether the mailbox exists. It does not tell you:

  • Whether the address is a spam trap
  • Whether it belongs to a role inbox like info@ or sales@
  • Whether the domain is dead or parked
  • Whether the person ever consented to receive your mail

A validation pass can remove obvious bounces, but it cannot replace a proper suppression strategy. Treating validation as a green light for sending is a common and costly mistake.

Spam traps, role inboxes, and dead domains

Spam traps are addresses that mailbox providers use to identify senders who do not manage their lists. There are two main types: pristine traps, which have never been used by a real person, and recycled traps, which were once valid but have been abandoned. Hitting either type signals that you are not cleaning your list.

Role inboxes such as info@, support@, or sales@ are not always harmful, but they often have low engagement and can generate complaints if used for prospecting. Dead domains, where the domain no longer resolves or the mailbox no longer exists, will produce hard bounces that damage your sender reputation.

A robust outbound setup blocks these categories before anything is sent. That means checking against known trap lists, identifying role addresses, and verifying domain status as part of your import process, not as an afterthought.

Persistent suppression across every campaign

One of the simplest and most effective reputation protections is a suppression list that applies across all campaigns. When someone unsubscribes or hard bounces, that address should be blocked everywhere, not just in the campaign where it happened.

Many teams run separate campaigns or use separate tools, and suppression lists live in silos. This means a contact who unsubscribed from one sequence can receive another sequence from a different part of the business. That is a fast track to complaints and, eventually, blocklisting.

A unified suppression list ensures that once someone says no, they are never contacted again. This is not just good practice for deliverability. It is also a basic requirement under regulations like GDPR and CAN-SPAM.

Building a reputation that travels with you

If you want to stop changing towns, focus on the fruit. That means:

  • Track the source of every contact and keep that record attached to the address.
  • Review import reports that show what was dropped and why, so you can fix bad sources.
  • Block spam traps, role inboxes, and dead domains before sending.
  • Apply unsubscribes and hard bounces across every campaign and every tool.
  • Monitor engagement by source so you can double down on what works and cut what does not.

None of this is glamorous. It is list hygiene and process discipline. But it is what separates senders who maintain stable deliverability from those who are perpetually looking for the next town.

A note on authentication

SPF, DKIM, and DMARC are foundational. SPF tells mailbox providers which servers are allowed to send for your domain. DKIM adds a cryptographic signature that verifies the message was not altered. DMARC tells providers what to do if authentication fails and gives you reporting on who is sending as your domain. These are table stakes, but they are not a substitute for list quality. You can have perfect authentication and still land in spam if you send to people who do not want your mail.

The takeaway

Changing domains is a temporary fix that does not address the root cause of reputation problems. The root cause is almost always the list: where it came from, how it was validated, and whether you remember who already said no. Fix those things, and your reputation will follow you to any domain you choose to send from. Keep skipping the inspection, and you will keep moving towns until there are no towns left.