Your domain got away from you. Here is how to get it back.

A lot of Canadian business owners find out the hard way that the web address printed on their truck, their invoices and their business cards is not registered in their name. It is registered to the person who built the site. Usually nobody set out to trap anyone. The domain got bought in a hurry during the build because it was faster that way, it went on their card, and nobody thought about it again until the day you needed to move, update something, or simply get an answer from someone who has stopped replying.

The good news is that a domain is one of the more recoverable pieces in this situation, and most cases end without any real argument. What you need is a clear picture of who actually holds it, a calm approach in the right order, and a plan for the messier version where the other side is not helping. Here is how that works in plain terms, with no assumption that you know what a nameserver is.

Step one, find out who actually controls it

Before you send a single message, find out where the domain lives. A WHOIS lookup is the standard way to check. You can use the lookup tool on almost any registrar's website, or the official WHOIS search that CIRA runs for .ca addresses. Type in your domain and you get back a record showing the registrar, meaning the company the domain is registered through, along with the creation date, the expiry date, and the current nameservers.

Expect the personal details to be hidden. Privacy rules mean most registrars, and CIRA for individual registrants, now redact contact information by default, so you may see a company name and nothing else. That is normal and it is not a dead end. The registrar name and the expiry date are the two facts that matter most right now. The registrar is who you will eventually be dealing with, and the expiry date tells you how much time you have before the domain lapses and becomes available for anyone else to register.

Registrant, contacts and account holder are three different things

This part confuses nearly everyone, and it is worth understanding because the wrong assumption costs weeks. The registrant is the recorded holder of the domain, the name in the "this belongs to" field. The administrative and technical contacts are the people listed to receive notices and handle changes. The registrar account is the login that controls all of it in practice, and that is the one that decides what actually happens.

You can have your business name sitting in the registrant field and still be unable to touch the domain, because someone else holds the login. You can also have a domain sitting in an account created with your builder's email address, where every renewal notice and every transfer approval goes to an inbox you cannot open. So when someone tells you "the domain is in your name," the question to ask is whether you can log in, change the details and move it. Only that last one is real control. It is the same distinction that decides who really owns your website.

How a domain transfer actually works

A transfer sounds technical and is mostly clerical. To move a domain from one registrar to another, three things generally have to happen at the current registrar. The domain has to be unlocked. An authorization code, also called an EPP code, auth code or transfer key, has to be released to you. And the transfer has to be approved, usually by a confirmation email sent to the contact on file. You then start the transfer at your new registrar, paste in the code, pay for a year of registration, and wait. It commonly takes about five to seven days for addresses like .com, and it is often quicker for .ca.

There are a couple of built-in delays worth knowing about so they do not feel like sabotage when you hit them. A domain registered or transferred within roughly the last sixty days is normally locked against another transfer, and changing the registrant details can start its own lock period too. Those rules come from the registry, not from the person you are dealing with. It is also worth knowing that your website and email do not go dark during a transfer. As long as the nameserver settings stay the same, everything keeps working while the paperwork moves.

If they cooperate, keep it short and specific

Most of the time the other person is disorganised rather than hostile, and a friendly, specific message gets it done in a week. Vague requests get vague answers, so ask for exactly what you need. Something like: "Please unlock yourbusiness.ca, send me the authorization code, and approve the transfer request when it arrives. I have set up an account at this registrar under this email address." Give a date you would like it done by, and offer to cover the renewal so money is not the sticking point.

If the domain simply sits in their account and you both agree it should not, there is an even easier route. Most registrars let one customer push a domain straight into another customer's account at the same company, which is usually instant and free, with no code or waiting period. Whichever way it lands with you, finish the job properly: put your own email on the account, add your own card, turn on auto renew, switch on two step verification, and turn the registrar's transfer lock back on.

A domain you cannot log into is not a domain you own, no matter whose name is printed on the record.

If they will not cooperate

When messages go unanswered, or the answer is a flat no, slow down and build a record instead of escalating in the moment. Put your request in writing by email so there is a timeline nobody can argue about: what you are asking for, by when, and what you have already paid. Keep every invoice, contract, proposal and message thread. If you paid for the registration yourself, find the line on the bank or card statement that proves it, because that single line is often the most useful thing you own.

Then approach the registrar directly. Registrars deal with their account holder, so nobody is going to hand you someone else's account because you asked nicely, but they do have processes for disputed accounts and for records that are demonstrably wrong, and most will tell you what evidence they need. At the same time, read whatever you signed. Whether the domain was meant to be yours is usually a contract question rather than a technical one. None of this is legal advice, and if there is money in dispute or the other side is refusing outright, that is the point to check your agreement carefully and get advice from a lawyer rather than keep pushing on your own.

---

The .ca dispute route, at a high level

Canadian .ca domains are managed by CIRA, which runs a formal dispute process usually referred to as the CIRA Domain Name Dispute Resolution Policy. It is worth understanding what it is designed for. Broadly, it deals with registrations made in bad faith of names that are confusingly similar to a name or mark the complainant already had rights in, such as a registered business name or trademark. A panel considers the case, there are filing fees involved, and one possible outcome is that the domain is transferred.

That can fit a situation where someone registered your business name for themselves and is now holding onto it. It is not a general purpose tool for every disagreement with a former supplier, and an ordinary contract dispute is usually handled a different way. If you are considering it, read CIRA's own policy pages and get proper advice before you spend money on a filing. Generic addresses like .com have their own broadly similar process under the rules of ICANN, the body that oversees them, with the same caveat that it is aimed at bad faith registrations rather than billing disagreements.

Do not lose your email while you fix this

This is the part that catches people out. If your email addresses end in your domain, they depend on DNS records attached to that domain, and a careless move can take your mail down for days. Before anything changes, write down or screenshot your current DNS records, especially the MX records that route your mail, any TXT records used for SPF, DKIM and verification, and your A record and any CNAMEs. Ten minutes of copying beats a week of missed enquiries.

A registrar transfer on its own does not usually disturb any of this, because the nameservers stay where they are and DNS keeps answering. The risk shows up when you also move DNS hosting, or when the old provider deletes the zone once the domain leaves their control. So make changes at a quiet time of day, keep the old settings in front of you, and send yourself a test message before you call it done. If you are not confident with this part, it is worth an hour of someone's help rather than a gamble.

A few mistakes that make it much harder

The recovery itself is rarely the problem. These are what turn a two week job into a six month one:

• Letting the domain expire while you are still arguing about it. Renewing is always cheaper and easier than recovering.
• Chasing only by phone or text, so there is no written record of what you asked for and when.
• Approving a transfer request without checking which account it is actually going to.
• Changing nameservers "to be safe" before copying down your existing DNS records.
• Registering a slightly different domain out of frustration, then splitting your Google results, your signage and your printed materials across two addresses.
• Posting a public accusation while you still need the other side's cooperation to release the code.

How to make sure it never happens again

Once the domain is safely in your hands, spend twenty minutes making it permanent:

1. Hold the domain in your own registrar account, opened with an email address you control.
2. Use a business email for the account rather than a staff member's personal one, so it survives people leaving.
3. Turn on auto renew, keep a current card on file, and register for several years at once if you can.
4. Turn on two step verification and the registrar's transfer lock.
5. Record the registrar, the login email and the expiry date wherever your business keeps its important paperwork.
6. Give your web person access as a user or manager on the account, never ownership of it.
7. Get the arrangement in writing before any new work starts, so nothing depends on goodwill later.

Losing control of a domain feels much worse than it usually turns out to be. In most cases it is a paperwork problem with a clear order of operations, and a business that keeps calm, keeps records, and renews on time gets its web address back. The lasting fix is the boring one: hold the domain yourself, in an account with your name and your card on it, and hand out access rather than ownership. Related reads: what to do when your web developer disappears, what to do when someone will not hand over your website, and who actually owns your website.