Who Controls Your Business Domain? A DNS and Renewal Checklist
Document domain registration, DNS hosting, renewal ownership, recovery contacts, website and email dependencies, and controlled changes before access is needed.
The website works and email arrives, but nobody knows which account controls the company’s domain. Renewal notices go to a former employee, while the web designer and email provider each manage a different part of the setup.
A business domain ownership checklist makes those responsibilities visible before a renewal, staff change, or service migration creates an urgent access problem.
Start with a practical question: can an authorized person identify the providers, reach the accounts, and explain who approves changes?
SMART takeaway
Separate registration, DNS, website hosting, and email responsibilities.
Record the account owner, renewal decision, recovery route, and change approver for each service. A working website does not demonstrate that the business can administer its domain.
Make a simple provider map
Record the domain name, registrar, DNS provider, website host, email provider, and responsible people. Some services may share a provider or account; others may not.
The registrar manages the registration relationship. DNS management determines the records used by connected services. Website and email hosting have their own administration and billing arrangements.
Microsoft’s provider-identification guidance explains how registration and nameserver details can help identify the registrar and DNS hosting provider.
Treat lookup results as a starting point to confirm against authorized account records and provider support. They do not demonstrate that the person reading them controls the account.
Confirm who holds the registration relationship
Have the authorized business owner review the registrant and account information with the registrar. Record the business contact responsible for keeping it accurate.
If a vendor registered the domain, establish the documented ownership and administration arrangement. Do not assume that paying for a website automatically answers who holds the registration account.
Keep agreements and relevant billing references in the approved business records. An account handoff may require provider verification and coordination; it is not a reason to share a personal login informally.
Use the vendor access management guide to document the vendor’s role and the business’s recovery route.
Assign renewal responsibility
Record the expiration date, renewal owner, billing method, and where reminders are received. Have a backup owner who can act when the primary person is away.
ICANN’s renewal guidance recommends tracking expiration, maintaining contact details, and keeping payment information current when auto-renewal is used.
Auto-renewal is a setting to review, not a substitute for checking whether the account and payment arrangement are usable.
Choose a review date appropriate to the business. Verify renewal through the registrar’s trusted account route rather than clicking an unexpected payment request.
Test administrative access without changing records
Have authorized people confirm that they can sign in using the approved authentication method. Keep recovery codes and other secrets in the business’s approved secure storage.
Identify whether the recovery route depends on a person, phone, or mailbox that could become unavailable. Ask the provider about supported alternatives where the current arrangement is fragile.
Use individual delegated access where the service supports it and the arrangement fits the business. Keep administrative authority separate from routine editing needs.
The password manager rollout guide and offboarding checklist help connect account access with staff changes.
Record the services that depend on DNS
Have the technical owner document the current records and their purpose through the provider’s supported process. Include the website, email, verification entries, and other business services actually in use.
Keep an approved reference copy before a planned change. Record which provider or technician is responsible for each dependency.
The SPF, DKIM, and DMARC guide explains why legitimate mail-sending services need coordinated configuration. Removing an unfamiliar record without identifying its owner can create an avoidable investigation later.
Do not publish a full administrative export or confidential account details in a public handoff document.
Put DNS changes through a controlled handoff
For a planned website or email change, document the intended records, responsible implementer, approval, verification steps, and rollback decision.
Agree on the work window and the business contacts who can test the affected services. Do not treat “the page loads on my computer” as acceptance for email and every other dependency.
Use the website migration checklist when the work also changes hosting, URLs, or redirects.
If an unexplained account or record change appears, route it through the incident response plan. Routine cleanup and suspected unauthorized changes require different decisions.
Keep a compact ownership register
- Domain, registrar, and registration account owner
- DNS provider and authorized technical administrators
- Renewal date, payment owner, and reminder destination
- Verified recovery route and backup business contact
- Website, email, and other documented dependencies
- Current provider agreements and change-approval process
Review the register after a vendor change, employee departure, billing update, or migration. Include it in the website maintenance process.
SMART Solutions provides website development and improvements and technology support. Contact our team to review the website and connected-service handoff.
The useful result is a verified administrative path, not another spreadsheet nobody can act on. Confirm the providers and renewal owner first.