A domain can remain connected to your website and email during a registrar change, but only if its renewal date, account access, transfer status, and DNS records are managed deliberately. This domain renewal checklist and transfer guide gives you a repeatable workflow for preventing expiry, avoiding unnecessary downtime, and verifying that visitors and mail services still reach the right systems.
Overview
Domain renewal and domain transfer are related but different tasks. Renewal extends your registration with the current registrar. Transfer moves the registration to another registrar, usually while preserving the domain name itself. Neither task automatically moves your website files, hosting account, mailbox contents, or DNS configuration.
The most important distinction is between registration and DNS service. A domain may be registered at one company while its nameservers point to DNS hosting elsewhere. Your website may be hosted with a third provider, and email may use a fourth service. Before changing anything, document those relationships instead of assuming that the registrar controls every part of the setup.
Use this guide as a recurring tracker. Record the domain’s expiration date, renewal settings, nameservers, key DNS records, account owners, and transfer status. Then review the record before each renewal, registrar transfer, ownership change, payment update, or nameserver modification.
If the domain supports WordPress or another business-critical website, take a backup and consider using a staging workflow before making related hosting or DNS changes. The guide to setting up a staging website explains how to test changes separately from the live site.
What to track
1. Registration and renewal details
- Domain name and extension.
- Current registrar and the account or organization that owns access.
- Expiration date, renewal term, and whether auto-renewal is enabled.
- Payment method, billing contact, and backup process for payment failures.
- Domain privacy or registration-data settings, where available.
- Any renewal notices, verification requests, or account alerts.
Do not rely on a single email reminder. A card can expire, an administrative mailbox can become inaccessible, or a notification can be filtered. Store the expiration date in a shared calendar and in your operational documentation. Confirm that the people responsible for the domain can sign in and complete a renewal without waiting for one individual.
2. Transfer readiness
Before transferring a domain, confirm that the registrant or account holder information is accurate and that you can access the current registrar. Look for the registrar’s transfer-lock control and its authorization code, sometimes called an EPP code, transfer code, or auth code. The label varies by provider.
Check whether a recent registration, renewal, ownership update, or contact change has placed a restriction on transfer. Requirements and waiting periods can vary by domain extension and registrar, so use the current instructions shown in the registrar account or registry documentation. If a transfer is time-sensitive, resolve these questions before starting it.
Record the transfer request date, the new registrar account, the authorization-code request date, and the status shown by both registrars. Never publish an authorization code in a ticket, public document, or unsecured chat.
3. Nameservers and DNS records
Copy the current nameservers exactly before changing registrar settings. Then document the records that matter to your services:
- A and AAAA records: commonly used to direct the domain to web servers.
- CNAME records: often used for subdomains or third-party services.
- MX records: used to route domain email.
- TXT records: may contain SPF, DKIM, DMARC, verification, or other service data.
- CAA records: may limit which certificate authorities can issue certificates for the domain.
Do not change nameservers merely because you are changing registrars. If the existing DNS service is working, keeping the same nameservers can reduce the number of variables. If you do need to change them, copy the complete DNS zone first and plan for DNS caching rather than treating the change as instantaneous.
For email-specific checks, compare this record with the instructions in the SPF, DKIM, and DMARC setup guide. A website can appear healthy while email delivery fails because an MX or authentication record was omitted.
4. Service and access dependencies
List every service that uses the domain, including the main website, subdomains, email, analytics, payment pages, password resets, APIs, and certificate management. Confirm who can access the registrar, DNS host, website host, and email provider. Keep recovery methods current, but do not store passwords or transfer codes in this article or another publicly accessible document.
Cadence and checkpoints
A useful domain renewal checklist has both a regular review schedule and event-based checks. The following intervals are planning suggestions, not universal deadlines.
| Checkpoint | What to verify | Action |
|---|---|---|
| Monthly or quarterly | Expiration date, auto-renewal, payment method, account access, and alert recipients | Update the tracker and correct missing access |
| Several weeks before expiry | Renewal price and term shown in the account, DNS records, website, and email dependencies | Renew early enough to resolve billing or verification problems |
| Before a transfer | Transfer lock, authorization code, contact details, transfer eligibility, and nameservers | Export or record the DNS configuration and document the rollback plan |
| During a transfer | Status at both registrars and any approval or verification message | Respond only through the official account or trusted registrar channel |
| After renewal or transfer | Registration term, nameservers, DNS resolution, HTTPS, website forms, and email | Run a live verification checklist and save the result |
Keep renewal and transfer work separate where possible. If a domain is close to expiry, renewing it at the current registrar may be safer than combining an urgent renewal with a transfer. After the domain is stable, you can evaluate the registrar change with more time to handle restrictions or account issues.
How to interpret changes
Not every visible change indicates a problem. A registrar transfer may leave the website online because the nameservers remain unchanged. Conversely, a small nameserver edit can affect both the website and email even though the registration remains active.
Use a simple before-and-after comparison:
- Compare the domain’s expiration date and registration status with your previous record.
- Confirm that the nameservers are the intended ones.
- Resolve the root domain and important subdomains from more than one network or DNS-checking tool.
- Load the website over HTTPS and test a representative page, login flow, contact form, and any critical transaction.
- Send and receive a test email using the domain, if email is part of the setup.
- Check the certificate and browser security indicators after any DNS or hosting change.
If the website fails but email works, inspect web records and hosting configuration first. If email fails but the website works, inspect MX, SPF, DKIM, and DMARC records. If both fail after a nameserver change, compare the new DNS zone with the recorded copy. If only some users report an issue, allow for DNS caching while continuing to verify authoritative records and service logs.
Keep evidence of the last known-good state: a DNS export, screenshots of registrar settings, a backup, and a short test result. This makes troubleshooting faster than trying to reconstruct the configuration during an outage. For a WordPress site, the website backup and restore checklist provides a useful companion process.
When to revisit
Revisit this domain transfer guide on a monthly or quarterly cadence, and immediately after any event that changes ownership, billing, infrastructure, or access. At minimum, schedule a recurring review for every active domain and a separate review before its expiration date.
Open the checklist again when:
- A payment card, billing contact, or administrative email changes.
- A team member leaves or the domain account changes ownership.
- You move the website or email to a new host.
- You plan to change nameservers, DNS hosting, or certificate management.
- You receive an unexpected transfer, renewal, or verification message.
- A registrar changes its dashboard terminology or transfer workflow.
- Your domain extension or registry introduces different eligibility or transfer requirements.
For the next review, create one record per domain with these fields: expiration date, auto-renewal status, registrar, account owner, nameservers, DNS host, transfer lock, authorization-code location, website host, email provider, last verification date, and next review date. Mark each item as confirmed rather than assuming it is unchanged.
Finally, perform a live test after every renewal, transfer, or nameserver change. Visit the website, test a key form, verify HTTPS, and check domain email. If the site is hosted on WordPress, pair this review with the relevant WordPress hosting migration guide when a host change is involved. A short, repeatable verification routine is the most reliable way to prevent a routine domain task from becoming an avoidable outage.