MailerSend Gives Each Sending Domain Its Own Reputation
MailerSend now tracks reputation per domain, so one client's bounce spike pauses only that domain instead of every sender on the account.
MailerSend now tracks reputation for each sending domain separately, the company said in its Oct. 27 What’s New post. Trouble on one domain no longer pauses sending for the rest of an account.
Four statuses, applied per domain
Each domain gets one of four statuses, MailerSend said: Healthy, Under review, Rebuilding or Sending paused. The limits are the ones account reputation already used, now applied to a single domain. Healthy domains send at normal speed. Domains under review or rebuilding send at 10 requests a minute. Paused domains stop until they recover.
MailerSend said a domain with a problem is the only one affected. Other clients and users keep sending. There is no account-level pause.
An email and a webhook when a status changes
MailerSend sends an email and fires a webhook that identifies the domain whenever its status changes, the company said. The status shows in the dashboard under Emails > Domains next to each domain’s delivery metrics. The status can also be fetched through the API and the MailerSend MCP server. An agency can sync it into its own monitoring.
Only plans with multiple domains get it
MailerSend said the feature is available on plans that include multiple domains: Starter and Professional, including the 14-day trial. The company aimed it at service providers, software platforms and multi-brand businesses that send for many clients from one account.
MailerSend also recommended domain-scoped tokens and SMTP credentials. A compromised token for one client then cannot send as another. The company also pointed to custom access permissions and DMARC reporting for every sending domain.
The take
We think this fixes a design flaw for multi-client senders. Reputation judged for the whole account lets the sender with the worst list set the fate of every other sender. One client’s bad import should cost that client, and only that client.
Per-domain status is a containment tool. It only works if the domains stay separate in practice. Two clients that share a domain or a token can still hurt each other. Give each client its own sending domain and scoped token. Send the new webhook to a channel someone watches. Check each domain’s status through the API before a big send.
