Make an inventory of the domain's websites, email identities, recovery contacts, API callbacks, certificates and business references. Confirm who owns the decision and keep the appropriate data exports before cancelling any service.

1. Move account recovery addresses and administrative contacts away from mailboxes that will stop working. Confirm replacement addresses by completing the service's verification process.
2. Export or migrate website and email data, then establish any planned redirect or closure notice while you still control the domain and hosting.
3. Remove or update third-party custom-domain bindings, OAuth callbacks, webhooks and verification permissions that are no longer needed. A DNS deletion alone may leave a separate provider association active.
4. Decide separately whether to renew, transfer or allow the domain registration to expire. Review the actual cancellation and expiry process with us rather than assuming a DNS-zone delete cancels billing.
5. After the retention and transition plan is complete, remove unneeded DNS and hosting resources in a recorded order. Keep credentials, exports and audit evidence for the authorised retention period.

Test replacement contact routes, redirects and recovery addresses. Check the client area for the intended service cancellation and registration renewal status separately.

If a domain was removed too early, determine whether registration, DNS or only hosting was affected. Recovery options and times differ. Restore the still-controlled component or contact the responsible provider with the exact service identifiers.

• Why deleting a DNS zone does not cancel or release the domain registration
• Transfer operational control of a company domain when an employee leaves
• Build a domain portfolio inventory with accountable owners and recovery contacts
• Publish a null MX for a domain that intentionally receives no email

• Nabtech: terms and service conditions
• ICANN: domain name lifecycle