Keep the source record, responsible people and next operating decision connected in your own workspace.
Keep registration, expiry, ownership and hosting relationships together.
Record the domain, registrar, account owner, registration date and expiry date. A domain can support a website, email, a redirect or brand protection. Describe the purpose rather than assuming a domain without a live website has no value.
Verify the purpose with the responsible owner.
A hosting relationship in the workspace documents what your team has confirmed. Missing linkage does not independently test DNS or prove the domain is unused. Update the hosting details when the service is hosted elsewhere or mark the purpose clearly.
Confirm the hosting relationship from authoritative records.
Domain expiry can affect several services at once. Confirm provider dates and the person responsible for renewal. A stored expiry date is useful only while it remains current; verify it after transfers, renewals or changes to the registrar account.
Update the date after the provider confirms renewal.
Protect login references and recovery details with appropriate workspace permissions. Recovery information should remain available to authorised administrators during a handover, without exposing passwords in ordinary notes or notifications. Confirm that the recorded account is the correct one.
Review authorised access before a staff change.
Ask whether a domain is reserved for a product, campaign, redirect or brand requirement. Only after confirming purpose and commercial terms should the owner consider retirement. Keep the decision linked to any affected website and email dependency.
Record the reason before allowing a domain to expire.
Record the domain, registrar, account owner, registration date and expiry date. A domain can support a website, email, a redirect or brand protection. Describe the purpose rather than assuming a domain without a live website has no value. Verify the purpose with the responsible owner.
Domain expiry can affect several services at once. Confirm provider dates and the person responsible for renewal. A stored expiry date is useful only while it remains current; verify it after transfers, renewals or changes to the registrar account. Update the date after the provider confirms renewal.
A hosting relationship in the workspace documents what your team has confirmed. Missing linkage does not independently test DNS or prove the domain is unused. Update the hosting details when the service is hosted elsewhere or mark the purpose clearly. Confirm the hosting relationship from authoritative records.
Ask whether a domain is reserved for a product, campaign, redirect or brand requirement. Only after confirming purpose and commercial terms should the owner consider retirement. Keep the decision linked to any affected website and email dependency. Record the reason before allowing a domain to expire.
Protect login references and recovery details with appropriate workspace permissions. Recovery information should remain available to authorised administrators during a handover, without exposing passwords in ordinary notes or notifications. Confirm that the recorded account is the correct one. Review authorised access before a staff change.