Disabling Domain Forwarding on Secondary Domains

Last updated: October 15, 2026

Summary

Domain forwarding was disabled across all secondary domains managed by Unify. This was done as a precaution to avoid these secondary domains associated with our customers' primary domains. Secondary domains only need to send mail, not resolve to a website, so removing forwarding cuts the risk without affecting outbound sending. Primary domains are untouched.

Background

Secondary domains are look-alike domains registered alongside a customer's primary domain, used to send cold outreach so the primary domain's reputation stays protected. Many were set up with web forwarding, so visiting the secondary domain redirected to the customer's primary website.

SURBL is a blocklist of domains found in the body of spam messages, rather than of sending IPs. Receiving mail systems check the links in a message against it, so a listed domain can push mail to spam or get it rejected, whichever server sent it.

Why forwarding was disabled

A SURBL listing on a secondary domain was not contained to that domain while forwarding was on. Three things made it worse:

  • A live destination. A forwarding domain resolves and redirects, so it stays an active, reachable URI that filters and scanners keep re-evaluating.

  • Reputation linkage. The redirect connects the listed domain to the customer's primary website, and some filters and reputation services follow redirects, so the primary could inherit the damage.

  • No upside. Outbound sending from a secondary mailbox doesn't depend on domain forwarding, so the setting offered little upside while carrying risk.

With the volume of secondary domains involved, fixing this domain by domain would have left listed domains forwarding for days, so we turned forwarding off in bulk and handled delisting separately.

Customer impact

  • Cold outreach: no change. Mailboxes on secondary domains send and receive as before.

  • Visitors to a secondary domain: they no longer land on the primary website. Prospects who type the domain or click a bare link in a signature will see an error instead of a redirect.

  • Replies: unaffected. Reply handling depends on MX records, not web forwarding