When a web agency builds or maintains your site, it may handle domain settings, DNS, hosting, SSL/TLS renewals, and website updates. But who should own website domain and admin accounts? As a practical rule, your business should control ownership, billing, and account recovery. The agency should receive named, limited access for the work it performs.
Separating ownership from day-to-day responsibility can help prevent lockouts, missed renewals, and rushed changes when a vendor relationship ends. It also makes it easier to know who handles routine website upkeep, such as server patches, backups, and certificate renewal checks.
Ownership and access are not the same thing
Your company should be able to regain control of its critical website accounts without relying on a former agency contact. That means keeping business-controlled contact and recovery details on the accounts, understanding how to sign in, and knowing how to change or remove access.
An agency can still do its job without owning those accounts. Give its staff individual accounts or delegated permissions where the platform supports them. Avoid shared credentials when possible, and provide only the permissions needed for the assigned work. This follows the access-control principle of granting appropriate access rather than treating every user as an owner. See OWASP guidance on implementing access control.
Keep multi-factor authentication enabled where available. Make sure the recovery method belongs to the business, not solely to an individual agency employee. For practical background, review CISA’s guide to multi-factor authentication.

Decide who controls each website account
There is no single login that controls every part of a website. Domain registration, DNS, hosting, the content management system, and certificate management may each use separate accounts. Record who owns each account and who performs the routine work.
Domain registrar
Your business should be the registrant and retain access to the registrar account. Use a business-controlled email address for account notices and recovery, keep billing details current, and document how an authorized business contact can regain access. The agency can have its own delegated access if the registrar supports it. ICANN’s domain portfolio administration practices discuss the importance of managing registration and account information carefully.
DNS management
Your business should know which provider hosts its DNS and how to reach that account. An agency may make and monitor DNS changes, but document the approved process and retain a business-controlled way to access the settings. DNS changes can affect more than the website, including business email, so confirm the purpose and impact before making changes.
Hosting and server administration
Keep a record of the hosting provider, account owner, billing contact, and recovery path. If an agency manages a Linux server, clarify who applies security patches, monitors the server, maintains backups, and responds to urgent problems. The agency may handle those tasks, but your business should know what is covered and how to reach the relevant account or support channel. For more on ongoing server responsibilities, see what server management involves.
SSL/TLS certificates
Agree on who checks that the certificate is active, monitors automated renewals, and investigates a failed renewal or domain-validation problem. Automation can help, but it does not remove the need to know who receives alerts and who can access the DNS or hosting controls needed to resolve an issue. Let’s Encrypt explains renewal considerations in its integration guidance.
Website administrator accounts
Your business should have a separate administrator account that it can access, even if the agency performs most site updates. Give agency staff individual accounts with permissions that fit their duties. Remove or reduce access when someone no longer needs it, and avoid making a vendor’s personal email the only route back into the site.
Billing, recovery, and notifications
List the accounts that can incur recurring charges or send renewal and security alerts. Confirm that the business can receive those notices and update payment details. Keep recovery information current, and store account instructions in a secure business-controlled location rather than in an informal email thread.
Make responsibilities explicit
A short responsibility record can prevent uncertainty during routine maintenance or an urgent incident. For each account, note:
- The provider and account owner.
- The business contact responsible for billing and recovery.
- The agency contact or role responsible for day-to-day changes.
- How access is granted, reviewed, and removed.
- What is monitored, including renewals, backups, and security updates.
- Where to find instructions and who to contact if access fails.
Be specific about tasks rather than relying on a broad statement such as “the agency manages the website.” For example, identify who checks certificate renewal alerts, who approves DNS changes, and who verifies that backups can be restored. If the work involves Linux upkeep, document who schedules patches and how maintenance is communicated. See guidance for scheduling Linux security patches.
Prepare for an agency handover
Start a transition by confirming your business can sign in to the registrar, DNS provider, host, website platform, and any related account used to manage certificates or backups. Check that business contacts and recovery methods are current. Then document renewal dates, important DNS records, backup locations, and the process for restoring the site.
- Confirm that business-controlled contacts can access each critical account.
- Review current agency accounts and permissions, and identify any shared credentials.
- Record renewal responsibilities, notification recipients, and billing contacts.
- Document DNS settings and note which records support the website and business email.
- Confirm where backups are stored and how restoration is handled.
- Agree on a handover date and a process for transferring needed files and instructions.
- After the transition, remove or reduce former vendor access and update recovery details if needed.
Do not make broad DNS or hosting changes just to transfer ownership. Confirm what each setting supports, and coordinate changes with whoever maintains the site and email. A documented handover is safer than relying on memory or waiting until an account is urgently needed.
Frequently asked questions
Who should be listed as the registrant of a business domain?
The business should be listed as the registrant, with accurate business-controlled contact information. An agency can assist with management, but the company should retain a reliable way to access and recover the registrar account.
Should an agency use the client’s registrar login?
Prefer individual or delegated access for the agency rather than sharing the business owner’s login. This makes it easier to limit permissions and remove a specific user’s access when responsibilities change.
Who is responsible for renewing an SSL/TLS certificate?
Assign a named business or agency role to monitor renewal status, receive alerts, and resolve failures. The business should know who is responsible and how to reach the account or settings needed to address a problem.
What should a business get before ending an agency relationship?
Confirm access to the registrar, DNS, hosting, website administrator accounts, backups, and relevant billing and recovery details. Obtain documentation of renewals, DNS settings, and maintenance responsibilities, then remove or reduce the former agency’s access.
How can a business check who controls its domain and DNS?
Check the account records and contact details at the registrar and DNS provider. Confirm that an authorized business contact can sign in or recover access, and document who currently makes changes.
Keep control clear before you need it
Your business does not need to perform every website task itself, but it should understand who owns the accounts, who has access, and who handles renewals and upkeep. Zevonix provides website management and security and Linux managed services for businesses in Daytona Beach and surrounding areas. Review your account ownership and recovery details, then get in touch if you would like help organizing website responsibilities.