Unlock domain for transfer: Registrar Lock and transfer lock explained

You want to transfer a domain to CURIAWEB, but the transfer cannot be started or completed because the domain is locked? For certain top-level domains, a so-called transfer ban or a Registrar Lock be responsible for.

Such protection prevents a domain from being transferred to another registrar without the corresponding authorization. Therefore, the lock may need to be removed by the current registrar before the transfer.

Whether such a transfer lock exists and which rules apply depends on the respective domain extension and the registrar used.

Briefly explained: If a domain is locked against a registrar transfer, it may need to be unlocked before the transfer. For many generic top-level domains, a status like clientTransferProhibited point out such a transfer ban.

What is a Registrar Lock? #

A registrar lock is a security feature that can be used to prevent a domain transfer to another registrar.

The domain generally continues to function during this lock. Website, DNS, and email are not automatically affected by a mere transfer lock.

Rather, the registrar transfer is locked.

That is an important distinction: A domain can be locked for transfer and at the same time function completely normally from a technical standpoint.

clientTransferProhibited means that the domain name is locked against being transferred to another registrar. #

For domain extensions that use the corresponding EPP status codes, the following status may appear, for example:

clientTransferProhibited

Simply put, this status means that a transfer of the domain to another registrar is currently not permitted.

The prefix client indicates a status set by the registrar in the process.

For a desired registrar transfer, this lock may need to be removed by the previous registrar or via their domain management.

Important: The status clientTransferProhibited does not mean that your website has been blocked. It concerns the transfer of the domain between registrars.

Why are domains locked against transfers? #

A transfer ban is primarily a security measure.

Without appropriate protective mechanisms, an unauthorized registrar change could have significant consequences. A transfer lock therefore makes the unwanted transfer of a domain more difficult.

For domains that are not supposed to be transferred, such a lock is generally nothing unusual.

It only becomes relevant when you consciously want to initiate a domain transfer.

Must I unlock every domain before a transfer? #

No.

Domain extensions use different registration and transfer procedures. Therefore, it must not be assumed that every domain has the same status prior to a transfer or needs to be unlocked in the same way.

The distinction between generic top-level domains and country code extensions is particularly important.

Rules that you, for example, from a .com-Domain know, do not automatically apply identically to a .ch-Domain.

Does clientTransferProhibited also apply to .ch domains? #

The well-known EPP status codes and transfer rules of generic top-level domains should not be applied across the board to .ch be transferred.

.ch features its own registry/registrar system and corresponding procedures for registrar transfers.

If you a .chwant to transfer a domain, you should therefore use the transfer information applicable to this domain from the previous provider and not automatically look for one from the .comsearch for the unlock function known from the environment.

Note: „Unlocking a domain“ is not an identical process worldwide. The specific transfer method depends on the top-level domain.

Where can I unlock a domain? #

If your domain has a transfer lock managed by your previous registrar, you will often find the corresponding setting in their customer area.

Depending on the provider, the feature may be named differently, for example:

• Registrar Lock
• Transfer Lock
• Domain Lock
• transfer ban
• Unlock domain
• Approve transfer

The exact designation and position differ between providers.

If no corresponding function is available, it may be necessary to request the transfer release from the support of the previous registrar.

How do I know if my domain is blocked? #

For domain extensions with corresponding domain status information, the status of the domain can provide indications of a transfer lock.

A possible status is:

clientTransferProhibited

A transfer can also be identified as blocked by a specific error message from the previous or new registrar.

It is important to pay attention to the actual error message. Not every failed transfer is caused by a registrar lock.

Is a transfer code the same as the unlock? #

No.

These are two different components of a transfer procedure.

A transfer or auth code serves for the authorization of the transfer for corresponding domain extensions.

A transfer ban on the other hand, prevents the registrar transfer from being carried out.

Therefore, both points can be relevant in a transfer procedure:

1. The domain must be unlocked for transfer.
2. A valid transfer code must be available.

Which requirements actually apply depends on the respective TLD.

Practical Tip: If you already have a valid auth code, but the transfer is still rejected, check the domain status as well. An auth code does not automatically lift an existing transfer lock.

What is an auth code? #

An auth code is security-relevant information used with various top-level domains to authorize a registrar transfer.

Depending on the provider or system, you may also encounter terms such as:

• Transfer code
• Authorization Code
• AuthInfo-Code
• EPP code

You can generally obtain the required code from your previous registrar or its domain management.

Treat this code confidentially and use it exclusively for the intended domain transfer.

Why is my domain not transferable despite being unlocked? #

A lifted transfer ban does not automatically mean that all prerequisites for a transfer are met.

For example, a transfer can still fail if:

• the transfer code is incorrect or invalid
• another transfer lock applies to the domain in question
• a required confirmation is missing
• the domain has a status that does not allow a normal transfer
• the domain has already expired or is in a special redemption period
• a transfer period applicable to the TLD in question is active

Therefore, the specific error message of the transfer process should always be checked.

What does the 60-day lock have to do with the registrar lock? #

Certain generic top-level domains may have rules that prevent a registrar transfer for a specific period of time.

This can be relevant, for example, after a new registration or a previous registrar transfer. Depending on the procedure, certain changes to registration data may also play a role.

Such a time-based transfer lock is not the same as a regular registrar lock, which you simply deactivate in the customer area.

If a registrar transfer is not possible due to an applicable transfer rule, manually disabling a domain lock alone may not be sufficient for that reason.

Important: The frequently mentioned „60-day rule“ does not apply generally to every domain extension. Always check the rules of the specific TLD in question.

Why can a newly registered domain be suspended? #

For certain generic top-level domains, a registrar transfer may be temporarily restricted immediately after registration.

This is to be distinguished from a voluntary or administratively imposed transfer ban.

Therefore, if a recently registered domain cannot be transferred, you should not repeatedly try to simply turn the registrar lock on and off.

Check instead whether a transfer time restriction applies to the domain in question.

Why might a recently transferred domain be blocked again? #

Even after a completed registrar change, time restrictions for a further transfer may still apply to certain TLDs.

The specific rule in turn depends on the respective domain and registry system.

Among other things, this protects against a rapid chain of unwanted registrar changes.

Can changes to domain owner data affect a transfer? #

For certain top-level domains and transfer procedures, changes to the registration or owner data can affect a subsequent registrar transfer.

Therefore, in the case of a planned transfer, it is advisable not to make unnecessary changes to the domain owner or contact details immediately beforehand.

Whether and what kind of restriction results from this depends on the respective TLD and the specific registrar procedure.

Is an expired domain simply „blocked“? #

No. An expired domain and a registrar lock are different things.

Depending on their extension, domains can go through various status or lifecycle phases after expiration.

For certain TLDs, status values from a redemption period may occur, for example.

Such a domain cannot be transferred simply by disabling a standard registrar lock.

We will handle that separately under Domain expired or PendingRedemption: What does the domain status mean?.

serverTransferProhibited means that the domain name is locked against being transferred to another domain registrar. #

Next to clientTransferProhibited further status codes may occur in corresponding registry systems.

An example is:

serverTransferProhibited

The essential difference lies in the level at which the transfer ban was set.

A clientTransferProhibited-Status is set at the registrar level. A serverTransferProhibited-Status comes from the registry level instead.

Such a status therefore cannot necessarily be removed by a simple switch in the registrar's customer area.

Important: Not every status with the word TransferProhibited is the same. The exact status designation is crucial for troubleshooting.

What does pendingTransfer mean? #

For corresponding domain extensions, during an ongoing registrar transfer, the status:

pending transfer

appear.

This status does not indicate a normal registrar lock, but rather that the domain is already in a transfer process.

In this case, no attempt should be made to start additional transfer orders in parallel on a speculative basis.

Can I reactivate the transfer lock after the transfer? #

If the domain in question or the registrar supports a corresponding lock function, a transfer lock outside of a planned registrar change is a sensible security measure.

Following a successfully completed transfer, the domain can therefore be protected against unintended transfers again in accordance with the available security features.

The domain does not need to remain permanently unlocked.

Does unlocking affect my website or email? #

Simply removing the registrar lock usually does not change the DNS records, nor does it change the website or email configuration.

The domain will continue to point to the same nameservers and DNS targets unless you change them separately.

Unlocking merely serves to enable an otherwise blocked registrar transfer.

Do the nameservers change when unlocking? #

No.

Registrar lock and nameservers are technically different functions.

When you disable a transfer lock, the nameservers registered for your domain remain unchanged.

If you want to use your domain with the CURIAWEB nameservers afterwards, that is a separate change.

The CURIAWEB nameservers are:

ns1.curiaweb.ch
ns2.curiaweb.ch

You can find more information at Finding and correctly using CURIAWEB nameservers.

Do I need to change the nameservers before the transfer? #

No.

A domain transfer can generally be considered independently of a nameserver change.

If the website and email function correctly via the existing DNS infrastructure, it may be sensible to initially leave the nameservers unchanged during a pure registrar transfer.

This prevents unnecessarily changing multiple technical components at the same time.

What should I check before unlocking? #

Before releasing a domain in active use for a transfer, you should ensure that the transfer is actually intended and prepared.

Check in particular:

• to which registrar the domain is to be transferred
• whether you have access to the current domain account
• ob ein gültiger Transfer-Code benötigt wird und vorliegt
• ob für die TLD zusätzliche Transferbedingungen gelten
• ob Website, DNS und E-Mail während des Transfers unverändert bleiben sollen

Den gesamten Ablauf behandeln wir unter Domain transfer to CURIAWEB: How the transfer works.

Wie lange sollte eine Domain entsperrt bleiben? #

Eine Domain sollte nicht unnötig dauerhaft für Transfers freigegeben bleiben.

Wenn ein Transfer geplant ist, sollte die Entsperrung gezielt im Rahmen dieses Vorgangs erfolgen.

Nach Abschluss des Transfers können die beim neuen Anbieter verfügbaren Schutzmechanismen wieder verwendet werden.

Was mache ich, wenn ich keinen Schalter zum Entsperren finde? #

Nicht jeder Registrar verwendet dieselbe Benutzeroberfläche oder dieselben Bezeichnungen.

Wenn du keine Funktion wie „Domain entsperren“ oder „Transfer Lock“ findest, solltest du zunächst prüfen, welches Transferverfahren für deine Domainendung vorgesehen ist.

Bei manchen Anbietern erfolgt die Transferfreigabe gemeinsam mit der Anforderung des Transfer-Codes. Bei anderen wird sie separat vorgenommen.

Falls die Funktion nicht im Kundenbereich angeboten wird, wende dich an den bisherigen Registrar und frage konkret nach der Freigabe der Domain für einen Registrar-Wechsel.

Was mache ich, wenn der bisherige Anbieter die Domain nicht entsperrt? #

Zunächst sollte geklärt werden, warum die Domain nicht für einen Transfer freigegeben wird.

Es kann einen legitimen technischen oder administrativen Grund geben, beispielsweise einen Domainstatus oder eine für die betreffende TLD geltende Transferbeschränkung.

Bitte den bisherigen Registrar deshalb um die konkrete Begründung beziehungsweise den aktuellen Domainstatus.

Nur anhand dieser Information lässt sich beurteilen, welcher nächste Schritt erforderlich ist.

Warum sollte ich nicht mehrfach neue Transferaufträge starten? #

Wenn ein Transfer wegen einer Sperre fehlschlägt, sollte zuerst die Ursache behoben werden.

Mehrere neue Transferaufträge lösen einen Registrar Lock oder einen anderen blockierenden Domainstatus nicht automatisch.

Ein systematisches Vorgehen ist deshalb sinnvoller:

1. Domainstatus beziehungsweise Fehlermeldung prüfen.
2. Feststellen, ob tatsächlich eine Transfersperre besteht.
3. Transferbedingungen der betreffenden TLD prüfen.
4. Gegebenenfalls Domain beim bisherigen Registrar freigeben.
5. Gültigen Transfer-Code verwenden, sofern erforderlich.
6. Transfer anschließend erneut starten.

Wie lange dauert der Transfer nach der Entsperrung? #

Das Entsperren einer Domain bedeutet nicht automatisch, dass der anschließende Transfer sofort abgeschlossen ist.

Die Dauer hängt unter anderem von der Domainendung, dem jeweiligen Transferverfahren und gegebenenfalls notwendigen Bestätigungen ab.

Dieses Thema behandeln wir separat unter How long does a domain transfer to CURIAWEB take?.

Domain entsperrt – was kommt als Nächstes? #

Wenn für deine Domain eine Transfersperre bestand und diese erfolgreich aufgehoben wurde, prüfst du als Nächstes die übrigen Voraussetzungen des Transfers.

Dazu gehört insbesondere ein gültiger Transfer- beziehungsweise Auth-Code, sofern dieser für die betreffende Domainendung benötigt wird.

Anschließend kann der Domaintransfer zu CURIAWEB gestartet beziehungsweise fortgesetzt werden.

Währenddessen sollten Website, E-Mail und DNS nicht unnötig verändert werden, wenn diese bereits korrekt funktionieren.

Practical Tip: Ändere während eines laufenden Domaintransfers nur Einstellungen, die tatsächlich für den Transfer oder einen gleichzeitig geplanten Hostingwechsel erforderlich sind. Das erleichtert die Fehlersuche erheblich.

Summary #

Eine Transfersperre beziehungsweise ein Registrar Lock schützt eine Domain vor einem unerwünschten Wechsel zu einem anderen Registrar.

Bei bestimmten generischen Top-Level-Domains kann der Status clientTransferProhibited darauf hinweisen, dass der Registrar einen Transfer derzeit blockiert.

Wenn du die Domain bewusst zu CURIAWEB transferieren möchtest, muss eine solche Sperre gegebenenfalls beim bisherigen Registrar aufgehoben werden. Ein gültiger Auth-Code und eine entsperrte Domain sind dabei unterschiedliche Voraussetzungen.

Nicht jede fehlgeschlagene Übertragung wird jedoch durch einen Registrar Lock verursacht. Zeitliche Transferbeschränkungen, besondere Domainstatus, abgelaufene Domains oder Registry-seitige Sperren können ebenfalls einen Transfer verhindern.

Prüfe deshalb bei einem fehlgeschlagenen Transfer zuerst die konkrete Domainendung, den Domainstatus und die Fehlermeldung. Erst danach sollte die tatsächlich erforderliche Sperre oder Transfervoraussetzung gezielt bearbeitet werden.