Bizzit

Domains and DNS

Registrar lock stops an unexpected transfer. It does not point the website. Unlock only when you start a real transfer.

By Bizzit � � Updated

Domain lock: leave it on until you mean to transfer, not as a website setting | Bizzit guide

People unlock because a tutorial mashed transfer and connect. An unlocked name is easier to steal or to move by accident. Website CNAME does not require unlock. Someone who unlocked "to connect hosting" and left it unlocked for months. Lock is theft-adjacent hygiene. CNAME is the site. Separate switches.

Leave registrar transfer lock on while the domain stays at that registrar. Connecting the name to Bizzit Pro at $12 a month needs a web CNAME to slug.bizzit.io, not an unlock. Unlock when you intentionally transfer out, then use the auth code.

Who this is for

Someone who unlocked "to connect hosting" and left it unlocked for months. If that is not you, a different Bizzit guide will fit better, do not force this URL.

The actual answer

People unlock because a tutorial mashed transfer and connect. An unlocked name is easier to steal or to move by accident. Website CNAME does not require unlock. Lock is theft-adjacent hygiene. CNAME is the site. Separate switches. The short version is still the one in the box at the top of this page. The rest of the article exists so you do not have to guess the limits.

Do this in order

Connect with CNAME. Keep lock on. Unlock only in the transfer-out checklist.

  1. Confirm lock is on after purchase
  2. Add CNAME without unlocking
  3. If transferring out, unlock, get auth code, start gaining transfer
  4. Relock if you abort
  5. Keep WHOIS email working

What not to do

Do not unlock for Search Console TXT. Do not send auth codes in a brief to Cipher. That is the usual way a useful page turns into a doorway, a fake comparison, or a brief Cipher cannot honor.

How this shows up on Bizzit

We will not ask you to unlock as a default connect step. If a live UI ever does, that UI wins, and you should still know why.

Limits

Do not unlock for Search Console TXT. Do not send auth codes in a brief to Cipher.

Limits and caveats

Do not unlock for Search Console TXT. Do not send auth codes in a brief to Cipher.

If a sentence would require a competitor SKU we have not verified, or a statistic we did not measure, it does not belong here.

What to do after you read this

If this page answered the query, open Create with the nouns from your own business, not a slogan. If it did not, you are probably in the wrong cluster: go back to the blog hub or Domains and DNS. Do not spin a second URL for a synonym. One intent per page is the whole point of this library.

Tools that actually do this job

These are public pages. Use them when the job is this job. They are not a second product you have to buy.

Questions people actually ask

Does lock stop DNS edits?

Usually no. Lock is transfer. DNS records still edit. Confirm on your registrar.

60-day transfer prohibition?

A recent prior transfer can block another. Follow the registrar, not this blog's invented calendar.

Privacy and lock?

Both registrar settings. Neither is $12.

Stolen domain?

Registrar and ICANN-style processes. Not legal advice. Not a Bizzit SKU.

Start free