Changing Contact Handles during Transfers
Several TLDs support changing contact handles during the transfer process through CentralNic Reseller.
In our continuous effort to provide highly reliable API responses, when it come's to domain transfer requests (TransferDomain) including contact handles, the following change is implemented in our LIVE environment at Tuesday July 6, 2021:
a) For TLDs that do not support changing contact handles during the transfer process through CentralNic Reseller, Domain transfer requests containing contact handles (TransferDomain parameter owner/admin/tech/billingcontact#) will be aborted with an error message (error code 503).
Example:
b) If the parameter FORCEREQUEST=1 is provided, Domain transfer requests containing contact handles, will continue to work, even if the relevant TLD or registry backend does not support changing contact handles during the transfer process through CentralNic Reseller. The given contact information will be automatically suppressed in that scenario. This also applies to potentially submitted name servers (TransferDomain parameter nameserver#).
Example:
EPP
Using the CentralNic Reseller EPP API will automatically enforce the 'FORCEREQUEST=1' parameter during the transfer process, if transfer op='request' is set.
OT&E
All changes are available for testing in the CentralNic Reseller OT&E since April 27, 2021.
Fulfillment TLDs and TLDs with manual transfer handling
For Fulfillment TLDs and TLDs with manual transfer handling contacts can always be stated but there's no check if contacts can be changed upon transfer. Instead our Fulfillment Team will notify you accordingly.
