How do ISPs merge or separate domain reputations?

Say you've got two sending domains: orders@harborpost.net for transactional email and news@deepcurrent.io for your newsletter. You've set them up separately on purpose. But if a mailbox provider like Gmail or Outlook decides those two domains belong to the same organization, reputation problems at one can bleed into the other. So how does that linking actually happen?

The clearest mechanism is organizational domain logic. Mailbox providers don't just look at a subdomain or a sending domain in isolation. They often look at the root (organizational) domain behind it. So mail.harborpost.net and news.harborpost.net both trace back to harborpost.net, and reputation signals can flow across the whole tree. This is why a problem subdomain can drag the root domain into spam.

Beyond that, mailbox providers pick up on several other signals that suggest two domains are related:

• Shared sending infrastructure. If two domains are sending through the same IP addresses or the same ESP account, that's a clear connection. Shared IPs on a dedicated pool are especially visible.
• Shared authentication records. If your SPF includes the same sending service and your DKIM signatures point to the same selector or key, that links the domains at the authentication layer.
• WHOIS and DNS patterns. Same registrar, same nameservers, same registration date, same admin contact. These aren't always checked, but they can reinforce other signals.
• Behavioral overlap. Sending to the same recipient list from different domains is a strong signal. If harborpost.net and deepcurrent.io both email captain@lighthouse.com regularly, that pattern suggests they're related operations.

When mailbox providers decide two domains are linked, they may pool reputation signals across them. Good sending behavior on one can give a small lift to the other. But the reverse is also true, and that's the real risk. A shared reputation hit can take down multiple streams at once.

How to audit your own domain linkage

Start by asking whether your domains share any of the signals above. Check your SPF records side by side. If they both list the same ESP's include, that's a visible thread. Look at your sending IP ranges. If two domains share IPs, even on a shared pool, you don't have full separation. Check WHOIS for both domains. If the admin email or nameservers match, that's another tie.

So if you want genuine independence between domains, you need to remove the common threads. That means separate IP pools, separate ESP accounts or streams, separate DNS hosting where practical, and most importantly, keeping your sending lists clean and non-overlapping. You don't have to go that far for every domain, but if one stream is high-risk (like cold outreach), full separation from your transactional domain protects the stuff that matters most.

Not sure which of your domains are actually linked in practice? Our SOS hotline is free and we're happy to walk through your setup with you.