Why an unauthorized transfer matters
A domain name is managed through a registrar account. If someone moves the domain to a registrar they control, recovering control may be difficult and time-sensitive. The domain could continue resolving normally for a while, so a transfer is not always obvious to visitors. The risk is about who can manage the registration, including future changes to nameservers, contacts and renewal settings.
Transfer locks and authorization codes add separate checks to the process of moving a domain between registrars. Neither is a substitute for securing the account that controls the domain. Together, however, they make an accidental or unauthorized transfer harder: the lock must be removed, and the person initiating the transfer must generally provide a valid code.
What a domain transfer lock does
A registrar transfer lock is a setting that tells the registration system not to allow an ordinary transfer to another registrar while the lock is active. Registrars may label it “transfer lock,” “domain lock” or something similar. Keeping it on is a sensible default when you do not intend to transfer the domain. For many domains, an owner can check or change the setting in the registrar dashboard, though the exact controls depend on the registrar and domain extension.
A transfer lock is not a general freeze on every domain setting. Someone with access to the registrar account may still be able to edit DNS or nameservers, change contact details, or turn the lock off, depending on the account’s permissions. Some registries and registrars offer stronger locking services with additional checks for changes. Those services are distinct from the standard transfer lock and may require a separate setup.
What an authorization code does
An authorization code, sometimes called an auth code, transfer code or EPP code, is a credential used when requesting a transfer at the new registrar. Its purpose is to show that the requester has obtained the transfer credential from the domain’s current management account or process. The code is usually entered at the receiving registrar, not published in DNS records or placed on a website.
Treat the code like a secret. Request it only when you need it, and enter it directly into the intended registrar’s transfer form. Do not send it in a public ticket, paste it into a shared document, or give it to someone who contacts you unexpectedly about a transfer. If a code may have been exposed, ask your registrar how to invalidate or replace it. Procedures and code validity vary by registrar and domain extension.
Protect the account behind both safeguards
The lock and code are most useful when access to the registrar account is well controlled. Use a unique password and enable multifactor authentication if the registrar offers it. Keep account recovery methods and the registrant’s contact email current and secure; a compromised mailbox can undermine otherwise careful account settings. Limit administrative access to people who need it, and remove access when their role changes.
Pay attention to unexpected notices about unlocks, code requests, contact changes or transfer attempts. Rather than following a link in a surprising message, sign in through your usual route to the registrar and check the domain’s status there. If something looks wrong, contact the registrar through a support channel you have verified. This also helps avoid handing account credentials or a transfer code to an impersonator.
A careful workflow for a legitimate transfer
Before starting a planned transfer, confirm that you can access both registrar accounts and that the domain’s contact information is accurate. Record its current nameservers and key DNS settings, especially records used for web service and email. A registrar transfer does not necessarily mean a DNS hosting change, but knowing who hosts the DNS helps you avoid an unintended interruption. Also check for any transfer restrictions shown by your registrar.
When ready, unlock the domain, obtain its authorization code through the current registrar’s approved process, and submit the transfer request at the receiving registrar. Follow the confirmation steps presented by the registrars and monitor the domain until the transfer is complete. Then verify the nameservers, DNS service, renewal settings and account security at the new registrar, and enable its transfer lock. Keep the code private throughout; it is a tool for one controlled move, not information to store in a public domain checklist.



