Does Your Agency Own Domains? Ask Before You Pay

A Brisbane trades business loses a good commercial enquiry on a Friday afternoon. The prospect has checked the website, found an old mobile number and called someone who left two years ago. Fixing the site should be simple. Except the business owner cannot get in because the agency registered the domain, controls the hosting and will not return calls. Does your agency own domains? If you cannot answer that question with certainty, you have a business risk sitting behind your website.

Your domain is not just the address printed on your ute, proposal or email signature. It is a critical business asset. It can control your website, your email, password resets, enquiry forms and access to other services. When someone else holds it in their own account, they hold far more than a technical setting.

Does Your Agency Own Domains, or Do You?

There is a simple standard: the domain should be registered in your business name and held in an account you control. You should be the registrant, have access to the login and recovery email, and be able to renew, update or transfer it without asking a supplier for permission.

An agency can help you buy and set it up. A developer can manage technical records. Your IT provider can be given access where needed. None of that requires them to own the asset.

The distinction matters most when the relationship changes. Perhaps your agency closes down, changes staff, becomes hard to contact or simply is not delivering. Perhaps your business outgrows a basic website and needs a system that handles quoting, bookings and follow-ups properly. If the domain sits in your own account, changing providers is an administrative task. If it sits in theirs, it can become a negotiation at exactly the time you need to move quickly.

A supplier saying, “We manage it for you”, is not the same as you owning it. Management is a service. Ownership is control.

Why Domain Control Affects More Than Your Website

Many owners only think about the domain when it is time to renew the website. By then, it may be tied into much more of the business.

Your email addresses may use the domain. So can staff logins, cloud software accounts, online forms, calendars, mailing lists and payment platforms. If a former supplier controls the domain’s DNS settings, they may control where your email goes and whether your website is visible. Even a well-meaning agency can create a mess if nobody documented what was connected before a change was made.

The commercial cost is real. A clinic may miss patient enquiries when a website form stops sending. A professional firm may look careless when email bounces. A builder can lose confidence with a homeowner who sees a security warning or an expired site. These are not abstract technical problems. They affect jobs, cash flow and reputation.

Domain control also protects your ability to make decisions. You should be able to appoint a new provider because they are better suited to the next stage of your business, not because the old provider finally agrees to release your digital assets.

The Lock-In Usually Starts With Convenience

Most domain ownership problems do not begin with bad intent. You are busy running jobs, looking after staff, answering clients and getting invoices out. An agency offers to sort the domain, hosting and email in one hit. It sounds useful because it is useful - at first.

The problem appears when there is no clean handover path. The domain is registered under an agency director’s name. The only login uses their email address. Renewal notices go to an inbox you cannot access. The hosting account contains several unrelated client sites. Nobody has recorded the credentials or which services depend on what.

That arrangement is convenient for the supplier, not safe for your business.

There is a reasonable trade-off here. Some owners do not want to touch domain settings, and they should not have to. A DNS change made carelessly can interrupt email. The answer is not to manage every technical task yourself. The answer is to own the account while authorising an accountable technical partner to manage it properly.

What Proper Ownership Looks Like

A well-run digital setup separates ownership from day-to-day administration. Your business owns the account and approves who has access. Your provider documents changes, uses appropriate permissions and leaves the system understandable for the next person.

For a domain, that generally means the legal business owner is shown as the registrant, while the administrative contact and recovery details remain under the business’s control. Use an email address your business owns, not a developer’s personal address or a generic inbox that disappears when staff leave.

The same principle should apply beyond the domain. A website without access to its source code, hosting account or key third-party tools is only partly under your control. You may be paying for an asset that you cannot properly maintain, improve or move.

Before a project begins, ask for a written tool register. It should make clear what is being used, whose account each service sits in, what it costs, when it renews and who can access it. This is particularly useful once your website connects to forms, booking software, customer records, automation or internal workflow tools.

Questions to Ask Before You Sign

You do not need to become a web developer to protect yourself. You do need straight answers. Ask these questions before paying a deposit, not when the relationship has already gone sideways:

• Will the domain be registered in my business name and account?
• Which business email address will receive renewal and recovery notices?
• Will I have full access to the hosting account, website administration and source code?
• What happens if I choose another provider in two years?
• Can you provide a written register of every tool, login and recurring cost?
• Are there exit fees, transfer fees or proprietary platforms that prevent a clean handover?

Watch how the supplier responds. A good answer is specific and written down. “Don’t worry, we handle all that” is not an answer. Neither is a vague promise that you can have access later.

There are cases where a provider may use their own central account for a specialist paid service. That can be acceptable if there is a clear commercial reason, the cost is transparent and the exit process is documented. It should never be used as a shortcut to keep your core business assets out of your hands.

If Your Agency Already Owns the Domain

Do not panic, but do act while the relationship is still workable. Start by finding out the current registrar, registrant name, renewal date and account email. Ask for this in writing. Then request that the domain be transferred into an account created under your business email address.

A legitimate provider should be able to explain the process and help without drama. There may be transfer rules, timing restrictions after a recent registration or a need to update contact details first. Those are normal administrative steps. They are different from a supplier refusing to release an asset you have paid to build your business around.

While you are reviewing the domain, check the rest of the setup. Confirm access to hosting, website files, CMS administration, analytics, business email, form notifications and any paid tools. Change passwords where appropriate and turn on multi-factor authentication using a business-controlled device or authenticator.

Do not make random DNS changes in the name of taking back control. Record the current settings first, particularly email records. A careful handover protects continuity as well as ownership.

Ownership Creates Better Supplier Relationships

Some agencies treat ownership as a threat because they rely on dependency to retain clients. That is not a partnership. A confident engineering partner earns ongoing work through delivery, responsiveness and useful improvements - not by holding the keys to the building.

When you own every stage, your provider can focus on the work that matters: a website that gives prospects confidence, better enquiry handling, faster quotes, fewer missed follow-ups and systems that fit the way your team actually operates. The relationship becomes more practical because both sides know the assets are secure.

Archway Automation takes this approach from day one. The client owns the domain, source code, hosting account, administrative email and tool register, with a documented path to leave if needed. That is not a bonus feature. It is the minimum standard for building business infrastructure you can rely on.

Before you approve your next website project, ask to see where the keys will live. A supplier who is comfortable handing them to you is far more likely to be worth trusting with the work behind the door.