Domain Transfer Checklist: Avoid Website and Email Downtime

When domain transfer checklist becomes a problem, the fastest fix is not always the first fix you find online. A safer approach is to confirm what changed, protect anything that still works and troubleshoot in a sequence that preserves recovery options.

Confirm the symptoms first

Write down exactly what is failing, when it started and who is affected. Save the exact error message. Test from another device or connection where appropriate.

If a live business service is affected, consider web hosting migration before making broad changes.

Check recent changes

Look for plugin or theme updates, password changes, DNS edits, hosting migrations, PHP upgrades, security rules or mailbox configuration changes. Use the timeline to narrow the investigation rather than assuming.

Protect recovery options

Before editing files, databases or DNS, confirm you have a usable backup or another recovery path. For security incidents, preserve relevant logs before cleanup.

Where compromise is suspected, AWS setup should consider credentials, vulnerable software and the original entry point, not just suspicious files.

Work from the outside in

Start with domain resolution, SSL, hosting response and account status. Then move into WordPress, plugins, the database and individual devices. This avoids troubleshooting the application when the fault sits elsewhere.

Change one thing at a time

Record important settings, make one controlled change and test again. Multiple simultaneous changes make it difficult to identify what fixed or worsened the issue.

For infrastructure changes such as technical support, keep a short record of old and new values so rollback remains possible.

Verify the complete service

A homepage loading does not prove a website is healthy. Test forms, logins, checkout, inbound and outbound email, mobile access, SSL and other functions the business relies on.

Prevent a repeat

Document the cause and recovery steps. Keep domain, hosting and email ownership clear, maintain backups and updates, and record DNS settings and important third-party services.

Related troubleshooting guides

Also see Cloudflare 522 and 524 and WordPress Backup Strategy for related checks and preventative steps.

Separate registrar transfer from DNS hosting

Moving a domain between registrars does not automatically require changing the nameservers. If the existing DNS provider is working, keeping the nameservers unchanged during the registrar transfer can reduce risk. Treat registrar ownership, DNS hosting, website hosting and email hosting as separate components.

Record the complete DNS zone

Before starting, export or document A, AAAA, CNAME, MX, TXT and other important records. Pay particular attention to email authentication such as SPF, DKIM and DMARC. Losing one of these records can cause an apparently successful domain transfer to create email or verification problems later.

Check locks, authorisation and renewal dates

Confirm the administrative contact details, transfer lock status and any required authorisation code with the current registrar. Avoid leaving a transfer until immediately before domain expiry. After completion, verify nameservers and DNS resolution rather than assuming the registrar’s success message proves every service is working.

Verify services after completion

Once the transfer completes, check the public website, SSL certificate, inbound and outbound email, contact forms and any DNS-dependent verification services. Confirm the domain’s renewal setting and expiry date at the new registrar. A transfer is complete only when the services attached to the domain still behave normally, not simply when the domain appears in the new control panel.

Practical takeaway

For domain transfer checklist, diagnose before repairing. Confirm the scope, protect recovery options, check recent changes, test systematically and verify the full service afterwards.