How to Transfer a Domain to a Crypto-Friendly Registrar

What a domain transfer is

A domain transfer, in the sense people mean by domain transfer crypto, moves the sponsorship of a name from the registrar that holds it now to a registrar that has agreed to take it. The gaining registrar asks for the name. The losing registrar releases it after its own checks. The coin you use to pay the gaining registrar is a separate fact. Paying in BTC, USDT, or XMR does not, by itself, change who sponsors the name. A wallet transaction and a registrar transfer are different objects that happen to share the word transfer.

The usual gTLD path has a shape you can recognize even when the buttons use different words. The name is unlocked at the current registrar. A status that blocks transfers is cleared. You obtain an auth code from that registrar. You start the request at the gaining registrar and provide the code there. You approve the request if the losing registrar asks the contact on the name to confirm. You wait. DNS may keep working throughout if the nameservers do not change. None of those sentences is a promise that every extension uses every step. Country-code names, and some newer extensions, publish their own rules. Read those rules on the registrar that holds the name today.

A transfer is also not a renewal you can improvise, and it is not a way to escape a bill at the current registrar. Many moves add a year at the gaining registrar and require that the name be paid there. Some extensions do not add a year. The price you should compare is the gaining registrar's transfer or renewal price, not a slogan on a blog. This page will not invent another registrar's fee. It will tell you to read their pricing page on the day you move.

What this shop will not do with a transfer

BuyDomainsCrypto does not submit an inbound transfer in this build. It does not charge a transfer price. It does not pull a name away from Namecheap, Cloudflare, Njalla, Porkbun, or anyone else because you topped up a balance. The catalog prices, including a .com at $12.99 per year, are registration-year rates for a new catalog order. They are not a quote to move a name you already own. Registration in this build is a stub. Paying an order does not create a live registry registration. If the stub refuses a line or the call errors, that line returns to the USD balance. It is not sent back to a wallet.

Do not email an auth code, an EPP code, or a transfer secret to support@buydomainscrypto.net. Do not paste one into a ticket. Support cannot apply a code this shop does not submit, and a code in a mailbox is a secret you have now shared. If a signed-in form on this site ever keeps a code in the browser session, that storage is not a transfer and it is not a request to another registrar. Close the thought there. The honest use of this shop, today, is a new catalog name paid from the prepaid balance.

These pages also do not claim that BuyDomainsCrypto is an accredited registrar, and this build does not run a dispute desk that decides who owns a name. If a name is in a dispute, talk to the registrar that actually sponsors it and, if you need advice, to a lawyer. This guide is a checklist for a voluntary move. It is not a way to take a name from someone else.

Catalog rates, for a new order only: pricing. The order of a new purchase: how it works.

What to check before you unlock anything

Unlocking is the step people rush, and it is the step that should come last. While the name is locked, a stranger who learns an old auth code has a harder time requesting a move. Unlock only after you have chosen the gaining registrar, confirmed that they will accept the extension, and confirmed that you can pay them the way you intend. A registrar that advertises crypto and then routes you through a card processor, or through an ID check you will not pass, is not yet the registrar you should unlock for.

Check the extension itself. A .com at one shop is not evidence that the same shop transfers .io, .ai, or a country-code name. Some names require a local presence. Some cannot move at all and can only be registered again after they expire, which is a different and riskier plan. This shop sells the extensions in its catalog and does not transfer any of them in. If the name you hold is not a new registration you want here, this shop is the wrong destination, even when the coin list matches what you hold.

Check who the registrant is. If a privacy company or a custodian is the holder, you may have a contract to use the name and still be unable to start a transfer, because you are not the registrant. That is a feature of some privacy products, not a bug in the auth-code form. Read the agreement before you ask them to release anything. On this shop, a catalog order stays the customer's order. Domain protection does not put another company on the name as registrant. That distinction does not create a transfer-in. It only describes a new order, and the order is a stub.

Check the remaining term and the renewal price you are leaving. A name that expires in a week is a bad candidate for a move you do not yet understand. Renew first at the current registrar if the expiry is close, then transfer when there is time to fix a mistake. Also write down the nameservers, the DNS host, and any email that uses the name. A move that keeps nameservers can still break mail if the new registrar applies its own default DNS and you click through that default.

The auth code, without sending it here

The auth code is a secret the current registrar generates or displays for the registrant. Labels vary: auth code, EPP code, transfer key, authorization code. The function is the same. The gaining registrar submits it with the transfer request so the registry can see that the request is authorized. You copy it from the current registrar's own control panel, or from a message that registrar sends to the contact it already has. You paste it into the gaining registrar's transfer form. You do not post it on a social network, and you do not mail it to a shop that has told you it will not submit the transfer.

Treat a code like a password that expires. Many registrars can issue a new one and invalidate the old one. If you requested a code months ago and then did not move, generate a fresh code when you are ready, and assume the old one is burned. If a code was emailed to an address you no longer control, change the contact email at the current registrar first, wait until you can receive their mail, and only then request the code. This shop does not send mail, so it cannot be the place that delivers a code to you.

Some extensions do not use an auth code. A form that demands one for those names is the wrong form. The current registrar's help page for that extension is the source. If they say the move is a ticket, a registry form, or impossible, believe that page rather than a generic checklist, including this one.

Locks, the 60-day idea, and approval mail

Registrars show several locks, and they are not interchangeable. A client transfer lock, sometimes shown as a status that prohibits transfer, is the one you clear when you intend to move. A lock against updates is a different switch. Privacy, auto-renew, and two-factor login are not transfer locks, though a registrar may refuse to show the auth code until you pass its own login checks. Clear only the lock the transfer page names. Leave the others until you understand them.

A common gTLD practice is a waiting period of about 60 days after a new registration, and often about 60 days after a completed transfer, during which a further transfer is refused. Registrars differ on whether they opt out of a lock after registration. This shop does not administer that clock, and this page will not tell you the number of days left on a name it does not sponsor. Log in at the current registrar and read the status they show. If they say the name is too new to move, paying a different shop will not override that.

Approval is the step that fails when the contact email is dead. The losing registrar often mails the registrant contact and waits for a yes, or it lets you approve inside its own panel. If the public contact is a privacy address, the mail may go to the privacy provider or to the address the registrar stored behind it. Update the email you can actually open before you start, and watch that inbox, including the spam folder, until the request is done. Ignoring the mail can cancel the move or leave it pending until it expires. This shop will not see that mail, because it is not in the path.

TTL, nameservers, and what can break

TTL, the time to live, tells a resolver how long it may cache a DNS answer. It is not a transfer setting. If the gaining registrar keeps the nameservers you already use, resolvers can keep using the same answers and TTL is usually irrelevant to the move. If the transfer flow replaces your nameservers with the new registrar's defaults, visitors and mail follow the new zone, and anyone who cached the old answers keeps them until the old TTL runs out.

When you do intend to change DNS, lower the TTL on the records that matter — the website address, the mail records, and any verification records — a day or two before the change, at the company that hosts the zone today. A five-minute TTL set ten minutes before the cutover does almost nothing, because the previous TTL is what resolvers are still honoring. After the new records are in place and you have checked them, you can raise TTL again. Some resolvers ignore very low values and cache longer than you asked. Plan for a residue, not for a hard cut at one second.

Write down more than the website. Mail, password resets, payment provider checks, and app login links often depend on DNS records that are easy to forget. Export the zone if the DNS host allows it. A crypto-friendly registrar is not automatically a DNS host you want. You can often transfer the registrar relationship and leave DNS where it is. That split is the calm version of a move. This shop stores nameservers on a catalog order and does not offer a zone editor. Do not plan a cutover on a stub order.

Paying with crypto is not the transfer

A registrar can be crypto-friendly in several narrower ways. Some take a coin only as a balance top-up. Some name a stablecoin network. Some accept Monero. Some ask for an ID above a dollar amount or at signup. Compare those facts on their own pages before you unlock. This shop's coin list is BTC, BCH, LTC, XMR, ETH, USDT, USDC, BNB, TRX. USDT is on TRC-20, ERC-20, and BEP-20. USDC is on ERC-20 and BEP-20. BTC, BCH, LTC, and XMR are on their own networks. Lightning is not listed. The smallest top-up is $25.00. The quote is held for 30 minutes. An operator credits the USD balance after checking the transfer of the coin. None of that is an inbound domain transfer.

If the gaining registrar does take crypto, pay them the way their page describes, after the transfer request exists, and keep the domain request and the coin request separate in your notes. A transaction hash proves a coin moved. It does not prove a registry moved a name. Save both the registrar's request identifier and, if you need it, the coin record. Do not send either secret to a third site that is not part of the request.

On this shop the only crypto path is the prepaid balance for a new catalog order. The comparison of BTC, USDT, and XMR, and the longer buy guide, describe that path. Use them when you are registering a name here. Use someone else's transfer form when you are moving a name that already exists.

BTC, USDT, and XMR comparison. buy-with-crypto guide

A checklist before you move

1. Confirm you are the registrant, or that the holder has agreed in writing to release the name.
2. Confirm the gaining registrar accepts that extension and that you accept their price, their ID rules, and their coins.
3. Write down nameservers, mail records, and the expiry date. Renew first if expiry is close.
4. If DNS will change, lower TTL a day or more ahead at the current DNS host. If DNS will not change, leave TTL alone.
5. Make sure the contact email receives mail. Then request a fresh auth code, if that extension uses one.
6. Unlock the transfer lock. Start the request at the gaining registrar. Approve it if they ask.
7. Do not start any of those steps at BuyDomainsCrypto. This build will not submit them.

If you wanted a new name instead of a move, search the catalog and pay from the balance. A .com is $12.99 per year, the same to renew. Support for that order is support@buydomainscrypto.net.

Domain transfer and crypto: FAQ

Can I transfer a domain into this shop and pay with crypto?

No. This shop does not submit an inbound transfer and does not charge a transfer price. Paying with crypto tops up a balance that pays a new catalog order. A .com in the catalog is $12.99 for a registration year, not a transfer. Do not email an auth code to support@buydomainscrypto.net. Registration in this build is a stub, and the transfer path is not a live API.

What is an auth code, and who should receive it?

An auth code, sometimes called an EPP code or transfer secret, is a password the current registrar can show so a gaining registrar can request a move. You give it to the registrar that will actually submit the transfer, through that registrar's own form, not through email to this shop. This shop will not use a code you send, and a code kept in a browser session is not a transfer.

Does unlocking a domain move it?

No. Unlocking removes a lock that blocks a transfer request. The name stays at the current registrar until a gaining registrar submits a request and the request completes. Unlock only when you have already chosen that registrar and you are about to start. This shop is not that gaining registrar in this build.

What does TTL have to do with a transfer?

TTL is a caching hint on DNS records. A transfer of the registrar relationship does not, by itself, change nameservers. If you keep the same nameservers, you usually do not need to lower TTL. If you will change DNS at the same time, lower TTL a day or more ahead at the host that serves the zone, and remember that some resolvers ignore a very low value. This shop does not sell a DNS panel. It can store nameservers on a catalog order, and that order is still a stub.

Will a 60-day lock stop every move?

Not every name uses the same rule. Many gTLD names cannot transfer for about 60 days after they are registered, and often again after a transfer, unless the current registrar's own policy says otherwise. Country-code names often use a different rule, or no auth code at all. Read the current registrar's transfer page for the name you hold. This shop does not run that lock, because it does not submit the transfer.

Where do I ask a question about a move?

Ask the registrar that currently sponsors the name, and the registrar you intend to move it to. For a catalog question on this shop, open a ticket if you can sign in, or write to support@buydomainscrypto.net. Do not include an auth code, a seed phrase, or a password.

Other questions: support@buydomainscrypto.net. Do not send an auth code or a seed phrase.