About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Your business may depend on a domain name for its website, email and every certificate. Yet the name is often registered in someone else's account: a web agency set it up, a founder used a personal email address, or an employee who has since left created the login. When something goes wrong, nobody can tell who is allowed to act.
This is general information, not legal advice. In plain terms, three layers decide control. The registrant is the person or entity recorded in the registry as holding the domain. The registrar (and sometimes a reseller in front of it) is the company that processes the registration for you. The registrar account is the login that lets someone change settings such as DNS. Check all three, and make sure a business-controlled person or role mailbox sits behind each. This article covers .au domains using the auDA rules, and generic names such as .com using ICANN's policy. It does not cover other country domains.
Why it matters
Whoever controls the account can usually change where your website and email point. A CISA advisory on DNS hijacking describes attackers who compromise the credentials of an account that can change DNS records, redirect traffic, and obtain valid certificates for the victim's domain (CISA AA19-024A, read through an archive copy). It recommends multifactor authentication on registrar accounts.
Control can also be lost slowly. A .au licence that is not renewed enters a 30-day grace period during which, auDA says, your website and email services stop working, and after that the name becomes available to the public on a first-come, first-served basis (auDA, renew). auDA says the provider sends the reminder emails and that you should keep your contact details up to date. Our reading: that makes a departed employee's address a risk.
The registrant is the licence holder, not an owner
For .au names, the Licensing Rules say a licence does not create a proprietary interest in a domain name, and that "A Person does not legally 'own' a Domain Name" (definition of No Proprietary Rights, and paragraph 2.3.3). The registrant is the person issued the licence and recorded as registrant in the registry data.
Several obligations follow, all in paragraph 2.11 of the Rules:
- The registrant must keep the information in the registry complete, true and accurate, and tell the registrar of changes within 14 calendar days (2.11.8 and 2.11.9).
- The registrant must remain eligible for the namespace and keep an Australian presence (2.11.5 to 2.11.7). For com.au and net.au, the Rules require a commercial entity and a domain name that matches or relates to its name or offering (2.4.4).
- If the registrant ceases to exist, the licence is deemed cancelled 30 calendar days later unless documented evidence shows it was agreed to transfer to the current user (2.11.2).
- A registrant must not rent, lease, sub-licence or permit another person to use the licence, apart from a related Australian body corporate (2.11.12).
Our reading of the last point: where a supplier or agency holds the registration and you use the name, the arrangement deserves a look against paragraph 2.11.12. We do not offer an interpretation. Ask auDA or a lawyer.
The auDA page on transfers adds a point many buyers miss: "Note that buying a business does not mean the domain name licence is automatically transferred to the new owner." If the licence moves as part of a contract, the Rules (2.13.4) and auDA say the transfer must be requested within 28 days of the agreement unless it says otherwise.
The registrar of record, and the reseller in front of it
Every .au licence has a registrar of record, even when you bought through a reseller. The Rules define it as the registrar recorded in the WHOIS data. auDA's transfer page explains that a reseller may have no direct contract with the registrar of record, and that you can find the registrar of record using the WHOIS tool.
The public WHOIS shows a subset of the registry data. According to the auDA WHOIS Policy, that includes the registrar's name and abuse contact, the registrant's legal name and ID (for example an ACN or ABN), the name servers, the DNSSEC status and a status field. It does not show street address or phone numbers, and it does not show creation, renewal or expiry dates (paragraphs 4.2 and 4.5). Registrants can get the dates through their registrar or a password recovery tool.
The account login is a separate thing
The login to your registrar or reseller account is not the same as the authorisation code that proves you can transfer a domain. auDA says the code is "different from the username and password you may use to access your account" with your provider, because the code is unique to each licence while the account may manage many.
For .au, paragraph 2.12 sets the rules for the code:
- It is 13 to 32 characters, with at least one letter and one number, and no dictionary words.
- The registrant must take reasonable measures to secure it and report if it is lost, stolen or known to someone else.
- A registrar may give it out only after being satisfied that the registrant authorised the request, and only to the relevant registrant contact in the registry data, unless the registrant gave written authority for a third party.
- The registrant must change it within two calendar days if the licence moves to a new registrar.
auDA's additional services page says the recovery information is sent to the registrant contact email address in the registry, and cannot be redirected. Our reading: the registrant contact email is therefore a key control. If it is a former staff member's mailbox, whoever controls that mailbox can request the code.
What a transfer needs
For .au there are two kinds of transfer, both in paragraph 2.13:
- Change of registrant. The current registrant requests it in writing through a registrar. The new holder must meet the eligibility rules, sign a new licence agreement and pay a fee. The Registrar must complete it within two calendar days of the request. A fraudulent transfer is cancelled (2.13.7).
- Change of registrar. The registrant requests it in writing and supplies a valid authorisation code. Registrars may not charge for it (2.13.9). auDA says it can take up to three days to take effect.
Neither transfer can proceed while the licence is subject to a complaint process, a dispute resolution process or court proceedings.
The ICANN policy for generic top-level domains such as .com is a different regime. Under the Transfer Policy as updated 21 February 2024, the registered name holder is the party with authority to approve or deny an inter-registrar transfer, and the policy says the transfer authorisation code (AuthInfo) is used to identify that holder. A registrar may set a transfer-prohibited status (a registrar lock) on request, and on your request the registrar (section 3.7.4) must either remove the lock or provide a reasonably accessible method for you to remove it, within five calendar days. After a change of registrant, the registrar "must impose a 60-day inter-registrar transfer lock", unless the holder opted out beforehand.
We did not find in the auDA pages we read any equivalent of a customer-facing registrar lock for .au, so treat that as not verified. Ask your registrar what additional protections it offers and whether it applies any lock or confirmation step to transfers and changes.
Putting your domain in order
Our recommendation, in this order:
- Identify the registrant. Look the domain up in WHOIS. Is the registrant the legal entity that runs the business, with the right ABN or ACN? If it is a person, a supplier or a closed company, plan a change of registrant.
- Identify the registrar of record and reseller. Write down both, with the support contact for each.
- Identify who can log in. Ask who has accounts, who the account owner is, and whether the login belongs to a named person who may leave. Prefer at least two named administrators within the business, and turn on multifactor authentication.
- Check the registrant contact email. It should be a mailbox controlled by the business, such as a monitored role address, not a personal one. Keep it current, because notices and authorisation code recovery use it.
- Check the expiry and renewal arrangement. Confirm who pays, which payment method is on file, and that reminders reach someone.
- Keep a record. Put the registrant, registrar, account owners and renewal date in one document that is reviewed after each staff change.
Read-only checks
None of these change anything. They use public lookups and your own records.
- Look up the domain in the official WHOIS service. For .au the WHOIS service is provided through a web tool, port 43 and RDAP, according to the WHOIS Policy. Note the registrant, registrar, status and name servers.
- Ask your registrar or reseller to show you, without changing anything, the account owner, the registrant contact email and any lock or confirmation setting.
- Check that the DNS provider shown by the name servers is the one you expect, and who holds that account.
- For .au, confirm the contact email address in the registry matches a mailbox you control. Only the registrant contact can receive the recovery email.
Questions to put to your provider
- Who is the registrant, and are you willing to transfer the licence to us in writing, with the transfer window the .au Rules require?
- Who holds the registrar account, and how do we obtain a login in our own name?
- Who receives renewal notices and the transfer authorisation code?
- What extra protections do you offer for changes and transfers, and how do you verify a request?
- If you are a reseller, who is the registrar of record?
A worked example (illustrative)
The following is invented. A firm discovers that its com.au domain is registered in the name of a former sole-trader web designer, with the designer's old mailbox as the contact. The reseller's account is also in the designer's name. The domain is due to renew in six weeks.
The firm cannot prove its right to the name by owning the account, because the Rules call it a licence, not ownership. It asks the designer to request a change of registrant to the firm in writing through the reseller, which the firm checks meets the commercial-entity and name-match rules. It gets the new registrant contact set to a role mailbox, changes the authorisation code after the move, and turns on multifactor authentication on a new account in its own name. It records everything in one page and sets a calendar reminder 90 days before expiry, the earliest renewal point the Rules allow.
Read next
Related articles you may want next.
- HostingFinding every certificate before it expires: certificate transparency logs and endpoint readsUse certificate transparency logs and endpoint reads to find forgotten, unknown or unauthorised certificates for your domains before they expire.Read article
- HostingShorter TLS certificate lifetimes: the 2026 to 2029 schedule and what to automateThe CA/Browser Forum schedule cutting TLS certificate lifetimes to 200, 100 and 47 days, and how to decide which renewals to automate first.Read article
- HostingReplacing a certificate after its private key is exposed: how fast revocation must happenA leaked certificate private key needs a new key, a new certificate and a prompt revocation request. What the 24-hour rule covers, and how optional OCSP changes it.Read article
Risks and limits
- This is general information, not legal advice. Rules and policies change; each was read as displayed on 15 November 2026.
- The .au Rules apply to licences created, transferred or renewed after 12 April 2021. Earlier licence periods may follow legacy rules.
- ICANN's policy does not govern .au. The two regimes differ, and other country domains differ again.
- Registrars and resellers set their own procedures within the rules.
- We did not verify any .au registrar lock feature.
- Our reading of paragraph 2.11.12 is a question, not an answer.
Next step
Look up your main domain in the official WHOIS service this week, and write down the registrant, the registrar of record and the person who owns the registrar login. If you are reviewing hosted networking and DNS, the Networking page is a starting point for that conversation; ask for the scope in writing.
Sources
- .au Domain Administration Rules: Licensing, auDA, Policy 2019-01, date approved shown as 22 June 2026.
- WHOIS Policy (2025-11), auDA, date approved shown as 4 February 2026; version history lists 1.2 of 23 June 2026.
- How to transfer your .au domain name, auDA, date unavailable.
- Additional .au domain services, auDA, date unavailable.
- How to renew your .au domain name, auDA, date unavailable.
- Which rules apply to my .au domain name?, auDA, date unavailable.
- Transfer Policy, ICANN, updated 21 February 2024.
- DNS Infrastructure Hijacking Campaign (AA19-024A), CISA, last revised 13 February 2019 (read through an Internet Archive copy captured 20 October 2026, which carries CISA's archived-content notice).
All accessed 15 November 2026.
Learning notes
- A domain is usually a licence, not property. The registrant is the licence holder.
- The registrar holds the registration. The registrar account login is a separate thing and controls DNS changes.
- The transfer authorisation code is different from your account password and goes to the registrant contact email.
- Buying a business does not move the domain automatically. The transfer has to be requested.
- Put the registrant, account and contact email in business hands, and review them whenever staff change.
This article was originally published on .