Changing Your Sending Domain Without Losing Reputation

Your store is rebranding, or you have decided news.store.com should carry campaigns so the root domain stays clean for receipts. Both are legitimate. Both fail the same way: the new name is mailed to the full list on day one, authentication is half-published, and Gmail treats the domain as a stranger because it is one.

Reputation does not transfer because you updated a setting. What a sending domain is is the definition. This page is the cutover. If you are only adding a platform and keeping the same From domain, use the ESP migration guide instead.

Last verified: 26 September 2026.

What you are actually changing

The domain in the From address is what DMARC aligns to. Gmail, Yahoo, and Microsoft evaluate that domain once you are in their bulk or high-volume rules.

• Gmail’s bulk sender definition is close to 5,000 or more messages to personal Gmail accounts within a 24-hour period. Bulk senders need SPF and DKIM, DMARC at least p=none, alignment, and one-click unsubscribe on marketing mail.
• Yahoo’s bulk rules: SPF and DKIM, DMARC must pass, complaint rate under 0.30% on mail that reached the inbox.
• Microsoft: senders of more than 5,000 emails a day to Outlook.com, Hotmail.com, and Live.com must pass SPF, DKIM, and DMARC (at least p=none, aligned). Non-compliant mail has been rejected since May 5, 2025, with 550 5.7.515.

A brand-new hostname has to meet those rules as soon as your volume qualifies. Meeting them gets your mail accepted. It does not get it into the inbox, and a fully authenticated new domain can still land in spam if you point it at a cold list. It also does not get a grace period in those documents for “we used to send from the other domain.”

Subdomain, replacement, or both

How to set up the subdomain is the DNS and naming detail. Klaviyo’s custom sending domain setup is the Klaviyo click-path. Do not duplicate those steps here. Do not skip warm-up because the DNS panel turned green.

The cutover

Authenticate the new name completely. SPF includes only the services that will send as it. DKIM signs it. DMARC is published on it, not only on the parent, unless you have deliberately chosen a policy that covers the child and you have tested that it does. Domain alignment is the failure mode when the record exists and the From host does not match the signature.

Announce from the old address. Customers have filters on the old from-address. One short message from that address, with the new address written out, is the difference between “expected” and “who is this.” Send it before the new domain carries a sale.

Warm with people who already interact. Recent clickers, modest volume, no win-back in the first sends. A win-back is a complaint engine on a domain that has no track record. List hygiene still applies. The new domain does not make a stale list safer.

The warmup checks, in order:

• The new domain authenticates on a message you received, not only in a DNS tool.
• The first sends are recent buyers or clickers. Volume stays at that slice until placement at Gmail, Yahoo, AOL and Outlook looks like mail you would trust.
• Bounces on that slice are mailbox-unknown, not a policy 5xx. A policy code means stop. Warmup failure is the stop. There is no calendar row that overrides it.
• Receipts move last, after one real order has passed on the new path.
• You do not publish a day count. Providers do not provide one.

Read the message, not the checklist. SPF, DKIM, and DMARC on a received copy. Placement at Gmail, Yahoo, AOL and Outlook via seed mailboxes. Microsoft authentication rejections (550 5.7.515) come from the bounce log, because they happen at SMTP time and never reach a folder.

Expand, then move the rest of the streams. Campaigns first or flows first, but watch for both hitting the same person. Transactional mail moves last, after a real order has passed authentication on the new path. If transactional mail is on SES, the SES guide covers the pause risk of sharing an account with marketing.

Turn the old domain off only when nothing still sends as it. Check review apps, the helpdesk, and the platform you think you cancelled. Leave DMARC reporting on long enough to see a leftover source. Then remove the old DKIM and SPF entries so they cannot be abused, and so you are not maintaining two looks-valid identities by accident.

There is no provider document that says reputation is “transferred” after a certain number of days. Judge the new domain by authentication, placement, and complaint rate. Judge the old one by whether it is still sending.

How to verify the new sending domain

• A campaign and, if applicable, an order message from the new domain show DMARC pass.
• Gmail Postmaster Tools is opened for the new domain, not only the old one. Compliance status and spam rate on the wrong hostname will look fine while the new name is in trouble. The Postmaster guide covers registering the hostname you actually sign.
• Yahoo’s complaint loop is enrolled for the new DKIM domain. Yahoo deliverability is the enrollment detail.
• The engaged slice is not in spam. If it is, stop the expansion. Why mail goes to spam is the next page, on the new domain.

Sending domain change mistakes to avoid

• Do not point the new domain at a purchased list to “build volume.”
• Do not set DMARC to p=reject on day one unless you have already watched reports and every legitimate source aligns. You will reject your own order mail.
• Do not change the from-name, the domain, and the ESP in the same send. You will not know which change the spam folder was answering.

What to monitor on each sending domain

Per domain, not as one blended account: Gmail compliance and spam rate, Yahoo complaints (in Yahoo’s own Sender Hub), authentication on each stream, and placement at Gmail, Yahoo, AOL and Outlook. DMARC monitoring checks each domain’s DMARC policy record every 24 hours and alerts on change. Spotting a leftover sender on the old name after the cutover takes aggregate reports, which InboxEagle processes as a separate paid product (DMARC Processing).

Sources

• Email sender guidelines, Google. Bulk authentication applies to the domain you send from, including a new one.
• Sender best practices, Yahoo. Separate bulk and transactional streams by IP or DKIM domain. DMARC must pass for bulk senders.
• Fix NDR 550 5.7.515, Microsoft. The From domain is what the rejection names.