Keep domain renewal notices reachable during an account handoff

Identify the registrar and responsible account

Ask who can sign in to the domain registrar, which mailbox receives important notices and who approves renewal payment. A vendor may maintain the website while the domain lives in a different account. Establish those facts before a staff member leaves or a service agreement ends. Do not infer ownership from who last edited the homepage.

Separate domain administration from website editing

ICANN recommends keeping registrar contact information current and paying renewal obligations on time. Domain-transfer rules and account changes can have additional conditions, so use the current registrar process for your situation. This guide is an operational handoff checklist, not a determination of legal ownership or a promise that a transfer can happen immediately.

Source checks: ICANN: Renewing Domain Names · ICANN: FAQs for Registrants: Transferring Your Domain Name

Verify renewal access before the handoff ends

Have the business owner inspect the account through an authorized sign-in rather than exchanging passwords in an email thread. Record the registrar, renewal date, contact mailbox, billing responsibility and account-recovery owner. Confirm the listed mailbox is actually monitored. Coordinate proposed contact or transfer changes with the registrar before assuming they are routine website edits.

• Identify the current registrar and verify authorized business access to its account.
• Inspect the account's expiry, renewal status and applicable billing arrangement.
• Confirm who receives notices and whether that person can access the mailbox after the handoff.
• Document the owner and next review date without placing credentials in the public website.
• Use the registrar's supported procedure for any required account, contact or transfer change.

Avoid account changes that create new risks

Do not treat an automatic-renewal setting as proof that payment will succeed. Do not cancel an old mailbox before checking domain notices and recovery routes. An editor invitation does not transfer registrar access. Avoid posting authorization codes or recovery information in shared marketing documents, and do not change nameservers merely to fix a contact mailbox.

Record verified dates and responsibilities

Record verified account access, current expiry information and notice ownership. Track unresolved handoff items with a responsible person and due date. A successful sign-in proves current access, not indefinite control or future payment success. Review the arrangement after changes in billing, staff or mailbox administration rather than relying on memory.

Schedule a review owned by the business

Keep a restricted business asset register with the domain name, registrar, account owner, renewal reviewer and last verification date. Separate it from customer-facing materials. Arrange a reminder owned by the business rather than a departing contractor. If facts are disputed or the domain is already expired, contact the registrar for the applicable recovery process.

Worked example: an illustrative customer journey

For example, a local service business changes website vendors. Its domain remains in a registrar account whose notices go to the former administrator. The owner verifies authorized account access and updates the monitored contact route through the registrar's procedure.

The asset register records the current expiry information and a business-owned review responsibility. The website remains a separate hosting item. This illustrates continuity planning; it does not determine legal ownership or guarantee that a pending transfer or future renewal payment will succeed.

Questions about this task