On this page9 sections
Why a domain move needs its own check
Moving a newsletter to a new sending domain looks like a settings change, but it changes the identity the recipient and the mailbox provider see. Authentication records, link domains, reply addresses, and consent records all have to line up before the first send. A rushed move can land the first campaign in spam or, worse, send from a domain that has no relationship with the audience. A short readiness check separates the technical cutover from the send itself. It also creates evidence that the team verified the move rather than assuming it worked.
Confirm ownership and DNS access
Start by confirming who controls the domain and who can edit its DNS records. Record the registrar, the DNS host, and the names of at least two people with access. Check that the domain is not already used for another sender or parked with a provider that blocks the required records. If the domain was purchased recently, confirm that it is not on a suppression or reputation list. Do not begin the move until ownership and access are written down. A cutover that stalls because one person is on leave is a preventable failure.
Publish authentication records before the first send
Set up SPF, DKIM, and DMARC for the new domain before any campaign is sent. Verify each record with the provider's tool and with an independent DNS lookup. Record the selector, the key, and the date each record was published. For DMARC, decide the policy the team can actually monitor, and do not jump to a strict policy without a reporting period. Authentication is not a one-time setup, because keys rotate and records drift. Add a monthly check to the operating calendar and name the person who owns it.
Align the visible and technical sender identity
The From name, From address, reply-to address, and envelope sender should tell the same story. If the newsletter moves to a new domain but the reply-to still points to the old one, replies can be misrouted and the recipient sees a mismatch. Update the visible footer, the unsubscribe link domain, and the physical address required by law. Test each link and reply path with a real message. The goal is a send where every identity the recipient can see agrees with the domain the team is authenticating.
Verify consent and preference records
Before moving, export the current consent state for the audience and confirm that it can be joined to the new sending system. Record how consent was captured, when it was last confirmed, and which tool holds the authoritative record. Check that unsubscribe and preference links still work after the move and that they update the same source of truth. Do not re-import an old list into the new domain without the consent evidence attached. A clean domain does not fix a consent record that was never clear.
Warm the domain with a small, engaged segment
Start with a small segment of recipients who have opened or clicked recently, and send content they already expect. Increase volume gradually while watching bounce, complaint, and reply rates. Record the volume, the segment rule, and the result for each send. Do not use the whole list to "test" the new domain, because a bad first impression is hard to reverse. The warm-up is evidence gathering, not a formality. If the results are poor, stop and investigate before increasing volume.
Check links, tracking, and unsubscribe behavior
Open the rendered message on desktop and mobile, follow every link, and confirm that tracking parameters and redirects resolve to the intended pages. Test the unsubscribe link from a real inbox and confirm that the preference is recorded in the authoritative system, not only in the sending tool. Check the reply-to address and the physical address in the footer. Save screenshots and the test record with the move checklist. These details are easy to miss because they live outside the campaign builder.
Prepare the rollback and the communication
Decide in advance what happens if the new domain underperforms. That might mean pausing sends, returning to the old domain for a period, or sending from a subdomain. Record the decision threshold and who can trigger it. Tell the audience only what they need to know, and keep the explanation simple. Do not announce a new domain before the authentication and consent checks are complete. A calm, specific note is better than a surprise change that looks like a phishing attempt.
Review the first month as evidence
After the first month, review delivery, complaints, replies, and unsubscribe behavior against the old domain. Compare like-for-like sends and note any change in audience or content. Record what the team learned and update the checklist. The move is complete when the new domain has a stable record and the team can explain how it was verified. A domain that sends without errors is not automatically a domain that is ready.
