Skip to main content
Visionnment Estimate value
Menu

Operator Systems

Domain, DNS, and Business Email Transfer Checklist

Use this domain, DNS, and email transfer checklist to sequence ownership, records, mail authentication, tests, rollback, access removal, and evidence.

A domain key moving through registrar, DNS, and business email checkpoints with a protected rollback route.

A domain, DNS, and business email transfer is not one switch. It is a sequence of ownership, naming, routing, identity, and recovery changes. Moving them all at once can turn one error into an unavailable website, rejected mail, and an account the buyer cannot recover.

Use this checklist to transfer control while services remain observable and reversible. It applies to an acquisition or an internal provider migration. Provider screens differ, so record the exact procedure and support contacts for the accounts in scope.

Difficulty: Intermediate
Plan window: Start discovery before closing; schedule risky changes during an agreed maintenance window
Prerequisites: Authorized seller and buyer operators, buyer-controlled accounts, current zone export, mailbox inventory, tested recovery contacts, and a written rollback owner

First five transfer phasesContinue with execution and acceptance in phases 6–8. Conceptual guide, not observed results.First five transfer phasesContinue with execution and acceptance in phases 6–81Inventory authority and dependencies2Establish buyer identities andrecovery3Design the sequence and rollbackpoints4Prepare DNS and mail authentication5Check domain eligibility andtransfer locks

First, separate the three control planes

Track these as distinct work items:

  1. Registration: the registrar, registered name holder, renewal, transfer lock, authorization code, and account recovery.
  2. DNS: the authoritative nameservers and the zone records that direct web, mail, verification, and other services.
  3. Email: the mail provider, users, aliases, groups, archives, routing, sender authentication, and administrative identity.

A registrar transfer does not inherently require a nameserver change. A nameserver change does not move mailboxes. A mailbox migration does not transfer the domain registration. Keeping those distinctions visible creates safer stop points.

Place this runbook beneath the broader website handover checklist and assign an accountable owner through the website SOP template.

Phase 1: Inventory authority and dependencies

Create one transfer register before changing anything.

Area Current control Target control Recovery contact Renewal/billing Dependencies Evidence Status
Domain registration Registrar and account Buyer account Buyer-controlled address Renewal owner/date Registry status, lock, DNSSEC Export/screenshot/ticket Open
Authoritative DNS Provider and zone Target zone Named operator Plan owner Web, mail, APIs, verification Zone export/checksum Open
Business email Tenant/provider Target tenant Break-glass owner License owner MX, SPF, DKIM, DMARC, apps User/routing export Open

Inventory at least:

  • exact domain spelling, registry expiration, registrar, registrant/account owner, nameservers, transfer status, and DNSSEC state;
  • every zone record, including root and www web records, subdomains, MX, TXT, CNAME, SRV, CAA, delegation, verification, DKIM, SPF, DMARC, MTA-STS, and TLS reporting records that are actually present;
  • mailboxes, aliases, distribution groups, shared inboxes, forwarding, catch-all rules, journaling/retention, delegated access, and application senders;
  • sites, CDNs, storage, APIs, payment systems, help desks, newsletters, calendars, login providers, and certificates that rely on the domain;
  • current administrative, billing, recovery, and abuse contacts.

Export the live zone from the authoritative source and capture record type, name, value, TTL, and provider-specific routing behavior. Also resolve the public records independently. A configuration screen can contain stale entries that are not authoritative.

Record current website and mail health: representative pages, certificate validity, inbound and outbound message tests, and mail headers. This becomes the baseline for acceptance and rollback.

Phase 2: Establish buyer-controlled identities and recovery

Before moving a critical asset, create named buyer accounts at the registrar, DNS provider, and mail service. Avoid a permanent shared login.

For every control plane:

  • verify the buyer’s legal/business profile where required;
  • add at least two authorized administrators where the provider supports it;
  • enable phishing-resistant MFA when supported;
  • store recovery codes and emergency procedures in the approved vault;
  • set buyer-controlled recovery email, phone, billing, and renewal alerts;
  • document support authentication requirements and escalation paths;
  • test that the buyer can sign in through a fresh browser session.

Do not make the domain’s recovery address depend solely on a mailbox under that same domain. If DNS or mail fails, the recovery route must remain available.

Phase 3: Design the sequence and rollback points

Choose the smallest set of changes necessary. A low-risk sequence often looks like this:

  1. reproduce and validate the DNS zone without delegating to it;
  2. prepare buyer mail identities, data migration, routing, and authentication;
  3. lower relevant DNS TTLs far enough in advance for older cached values to age out;
  4. change one control plane during the window;
  5. observe from independent networks and test critical journeys;
  6. proceed only after the acceptance gate passes;
  7. retain the old service for the documented fallback period;
  8. remove seller access after final acceptance, not at the first sign of success.

A lower TTL is not retroactive. Resolvers may retain the prior answer until its earlier TTL expires. Record when the lower value became authoritative and use that fact when setting the window.

Write rollback actions before the change: who decides, the last safe decision time, the values to restore, required credentials, expected recovery behavior, and how customers will be informed. Rollback is not guaranteed if registry, provider, or propagation constraints prevent an immediate reversal.

Phase 4: Prepare DNS and mail authentication

Copy only records that are understood and still required. Preserve exact syntax where a service depends on it, but investigate duplicate, conflicting, or unexplained entries rather than silently deleting them.

For business email, map:

  • MX: which servers accept inbound mail and in what priority order;
  • SPF: which systems may send using the domain’s identity;
  • DKIM: which selectors and public keys validate signed mail;
  • DMARC: how receivers handle and report alignment failures;
  • service verification and routing: provider-specific TXT/CNAME/SRV entries;
  • MTA-STS/TLS reporting: if deployed, the DNS and HTTPS policy dependencies.

The SPF specification, RFC 7208 says a domain must not publish multiple records that would cause more than one SPF record to be selected. Consolidate through the approved provider design; do not simply add a second policy. DKIM, RFC 6376 and DMARC, RFC 9989 describe separate authentication and alignment mechanisms, so a passing SPF lookup alone does not prove the whole mail identity is correct.

Prepare the target service before changing MX. Create users, aliases, shared mailboxes, groups, retention settings, and application senders. Migrate historical data through an approved method and record counts or provider reports. Do not copy passwords or MFA seeds between people.

Phase 5: Check domain transfer eligibility before closing

For generic top-level domains governed by the ICANN Transfer Policy, confirm the current rules and the registrar’s process. ICANN’s current Transfer Policy covers inter-registrar transfers, AuthInfo codes, lock status, and circumstances in which a transfer may be denied. Country-code and registry-specific domains may follow different rules.

Before scheduling the transfer:

  • verify that the Registered Name Holder can authorize an inter-registrar transfer; if a representative will act, confirm the registrar's supported process and the holder's authority rather than assuming a Change of Registrant agent has transfer authority;
  • check initial-registration, prior-transfer, change-of-registrant, dispute, court, and lock conditions;
  • decide whether the goal is an internal account push, a registrant change, an inter-registrar transfer, or more than one of those;
  • confirm whether changing registrant details first could trigger a lock;
  • obtain the AuthInfo code through the registrar’s approved route and store it as a short-lived secret;
  • verify that transfer confirmation messages reach a controlled address;
  • record expiration timing, fees, renewal behavior, and expected status transitions.

ICANN advises registrants whose final goal is a different registrar to consider the inter-registrar transfer before a change of registrant to avoid a possible 60-day lock, subject to the registrar’s available opt-out and the current policy. Treat this as a planning question, not a reason to bypass an identity or fraud control.

Confirm registrant authority and the actual lock before sequencing changes

Use the current ICANN Transfer Policy for covered registrar transfers. Identify the registered holder and distinguish a registrar transfer from a registrant change. A change of registrant can trigger a separate 60-day transfer lock; an advance opt-out is available only where the registrar offers it and it is exercised before the change.

Ask the registrar to confirm the domain's exact status, applicable timing and supported sequence. Do not assume the rules for one generic top-level domain apply to every country-code domain. Record renewal, dispute and recovery dependencies alongside the lock question.

If a registrar move must happen before an ownership-contact change, place both steps in the closing plan before anyone edits the account. Preserve the current DNS zone and mail records. A locked transfer need not mean that the existing website or email should be disabled. Acceptance still requires buyer-controlled authority, correct DNS responses and tested mail continuity; the account screen alone cannot establish all three.

Phase 6: Execute one observable change at a time

Open a live change record with the timestamp, actor, prior value, new value, approval, and test result.

If changing nameservers:

  1. confirm the target zone contains the approved records;
  2. validate DNSSEC sequencing with both providers before changing delegation;
  3. change the delegation at the registrar;
  4. query multiple public resolvers and the authoritative servers;
  5. test web, API, certificate, login, payment, and mail paths;
  6. compare returned records with the approved zone;
  7. stop if a critical record is absent or inconsistent.

If moving mail:

  1. complete the agreed data synchronization;
  2. activate the target identities and sender configuration;
  3. change the approved mail records;
  4. send inbound tests from unrelated providers;
  5. send outbound tests to unrelated providers and inspect headers;
  6. test aliases, groups, replies, calendar invitations, password resets, contact forms, help desk routing, and application mail;
  7. monitor queues, bounces, authentication results, and DMARC reports where available;
  8. run a final synchronization and preserve the migration report.

If transferring the registration, do not change DNS merely because the registrar changed. Confirm the nameservers and DNSSEC state before and after the transfer.

Phase 7: Accept the transfer with independent evidence

Use acceptance criteria, not “it works for me.” Confirm that:

  • registry/registrar records show the intended control and contacts;
  • renewal, billing, recovery, lock, and MFA settings belong to the buyer;
  • authoritative DNS answers match the approved zone;
  • website, certificate, API, and critical subdomain journeys succeed;
  • business email passes inbound, outbound, reply, alias, group, and application tests;
  • representative messages show the expected SPF, DKIM, and DMARC outcomes;
  • old and new services have no unexplained queue or sync gap;
  • an authorized buyer operator can complete recovery and routine administration;
  • the change log, exports, test artifacts, exceptions, and support cases are stored in the sale data room.

Keep time-stamped evidence, but redact authorization codes, recovery codes, message contents, and live secrets.

Phase 8: Remove residual access and close safely

After the agreed observation period and buyer acceptance:

  • restore normal TTLs where appropriate;
  • rotate registrar, DNS API, mail migration, application SMTP, and other scoped credentials;
  • revoke seller users, sessions, app passwords, OAuth grants, tokens, and delegated mailbox access;
  • remove obsolete routes, forwarding, temporary allowlists, and migration tools;
  • confirm backup, retention, legal-hold, and deletion responsibilities;
  • update vendor ownership, privacy contacts, SOPs, incident routes, and renewal calendar;
  • record remaining support obligations and the final acceptance date.

Coordinate those controls with the broader website handover access controls instead of treating email as the only identity boundary.

Worked continuity decision before changing to a sales lander

A hypothetical domain seller has an active website, a support mailbox and a transactional sender on the domain. A venue suggests pointing nameservers to a sales lander. That request changes authoritative DNS; it can affect more than the visible homepage.

The seller first exports the current zone and records this decision sheet:

Dependency Proposed change affects it? Safe preparation Stop condition
Website root/www Yes, if delegation changes Agree the intended destination and preserve old values Active customer journey would disappear without authorization
Support email MX Potentially Confirm mail records exist at the target authoritative service Target cannot retain the required records
Transactional SPF/DKIM Potentially Map all active senders and signing selectors Authentication records cannot be preserved or verified
Recovery address Potentially Test an independent recovery channel Access depends solely on affected mail
DNSSEC Potentially Get provider-supported delegation/DS sequence Validation state is unclear

The seller should ask whether listing can proceed without changing nameservers, whether only a specific web record must change, or whether the venue supports the full required zone. Do not invent a supported alternative: obtain the actual provider instructions. If the sales-lander setup cannot preserve necessary services, choose another supported route or delay the change.

For a bare domain with no website, mail or other dependencies, the inventory can be short. Confirm that absence rather than forcing a business-operation migration. Expiration, control, transfer eligibility and protected payment sequencing still matter.

When comparing venues, model the whole route. In a hypothetical comparison at the same $5,000 gross sale price, Route A has $500 of assumed transaction costs and $150 of supported transfer work, leaving $4,350. Route B has $400 and $350 respectively, leaving $4,250. These are invented cost inputs, not venue fees; replace them with current quotes. The apparently cheaper transaction fee does not establish higher net proceeds, and neither number prices the consequence of lost business email.

Use the current mail standard and observable tests

As checked on October 29, 2026, RFC 9989 supersedes the older DMARC specification. It links SPF/DKIM authentication to alignment with the author domain. A passing SPF result alone cannot establish DMARC success, and authentication success does not guarantee inbox placement.

Keep the migration test practical: send a permitted sample from each real sender type to unrelated recipient providers; inspect the authentication results and visible From identity; test replies and support routing; then compare the result with the approved configuration. This is an instruction for the authorized operator, not a claim that Visionnment ran the test.

If outbound mail works but support mail stops arriving, check authoritative MX answers and recipient-side queue/bounce evidence before altering unrelated sender policies. Restore the documented prior values if the incident owner authorizes rollback and the provider sequence permits it. Keep both configurations and timestamps; do not delete the original service merely because one test message succeeded.

Common transfer mistakes

  • changing registrar, nameservers, hosting, and mail in one unobservable step;
  • discovering a transfer lock after the closing window begins;
  • lowering TTL immediately before a change and expecting old caches to update;
  • transferring a domain while recovery remains tied to the seller;
  • copying a zone but missing DKIM selectors, subdomain delegation, verification, or application records;
  • adding a second SPF policy rather than designing one valid policy;
  • removing the old mail service before final synchronization and external tests;
  • revoking seller access before the buyer proves recovery and administration;
  • storing AuthInfo codes or recovery secrets in the handover spreadsheet.

The aim is not a claim of zero downtime. It is controlled change: one accountable owner, current evidence, small blast radius, explicit stop rules, and a tested recovery path.

Frequently asked questions

Should the registrar and DNS provider be moved at the same time?

Usually they can be separated. Keeping the existing nameservers through a registrar transfer reduces simultaneous change, but the actual choice depends on provider support, DNSSEC, account risk, and the deal timeline.

How early should TTL be reduced?

Base the lead time on the existing TTL and the resolver behavior you can observe. The lower value helps only after older cached answers expire. Restore an appropriate operational TTL after the migration stabilizes.

Can the seller just hand over one shared email administrator password?

That creates poor attribution and recovery risk. Add named buyer administrators, enable MFA, prove access, transfer services, then revoke seller access and rotate relevant secrets.

What evidence belongs in the handover record?

Keep dated zone exports, approved changes, provider transfer confirmations, non-sensitive configuration reports, mail migration results, independent test results, exceptions, and signed acceptance. Never attach live authentication or recovery secrets.