Domain Transfer Policy

Domain Transfer Policy

1. Scope
This Domain Transfer Policy applies to inter-registrar transfers of domain names sponsored by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") where the applicable top-level domain is subject to the ICANN Transfer Policy. Transfers of country-code top-level domains ("ccTLDs") may be subject to different or additional registry rules.

2. ICANN Transfer Policy Incorporated
For domain names subject to the ICANN Transfer Policy, NiceNIC will process transfer requests in accordance with the then-current ICANN Transfer Policy, which is incorporated into this Policy by reference.

Official ICANN policy:
https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy

If this NiceNIC summary conflicts with a mandatory provision of the ICANN Transfer Policy, the ICANN Transfer Policy controls.

3. Transfer Authority
For purposes of an ICANN-governed inter-registrar transfer, the Registered Name Holder is the party authorized to approve or deny the transfer, subject to the verification, authorization, security, and dispute procedures required by the ICANN Transfer Policy.

NiceNIC does not rely on an "Administrative Contact" as an independent transfer authority merely because older records or legacy systems may contain such a contact.

4. Transfers Away from NiceNIC
Subject to the ICANN Transfer Policy and applicable registry requirements, a Registered Name Holder may transfer an eligible domain name away from NiceNIC.

Where applicable:

the domain must not be subject to a transfer prohibition that is permitted or required under the ICANN Transfer Policy or applicable registry rules;
the Registered Name Holder may be required to unlock the domain;
the Registered Name Holder may be required to obtain the applicable AuthInfo/EPP authorization code;
NiceNIC may send transfer notifications required by ICANN or the registry; and
NiceNIC will approve, deny, or allow a transfer to proceed by default in accordance with applicable ICANN and registry timelines.
Where NiceNIC does not provide a self-service mechanism to obtain an AuthInfo code, NiceNIC will provide the code within the period required by the ICANN Transfer Policy after a valid request and any permitted identity or security verification.

5. Permitted or Required Transfer Denials
NiceNIC may deny, and in some circumstances must deny, an inter-registrar transfer only on grounds permitted or required by the applicable ICANN Transfer Policy or registry policy.

Such grounds may include, where applicable:

evidence of fraud;
a reasonable dispute over the identity of the Registered Name Holder;
specified non-payment circumstances permitted by the ICANN Transfer Policy;
an express and informed objection by the Registered Name Holder;
a transfer request made within an applicable ICANN or registry transfer-restriction period;
a pending UDRP proceeding;
a URS proceeding or URS suspension;
a court order from a court of competent jurisdiction;
a pending Transfer Dispute Resolution Policy proceeding; or
an applicable change-of-registrant transfer lock.
NiceNIC will not use the transfer process merely as a debt-collection mechanism where the ICANN Transfer Policy prohibits doing so.

6. Transfer Locks
Where a transfer lock is permitted, NiceNIC will provide a reasonable means for the Registered Name Holder to remove the lock where required by ICANN policy.

Security locks requested by the Registered Name Holder, registry-level locks, court-ordered restrictions, UDRP/URS-related restrictions, and other mandatory restrictions may be subject to separate procedures.

7. Transfers to NiceNIC
A person requesting a transfer to NiceNIC represents that they are the Registered Name Holder or are duly authorized to act for the Registered Name Holder.

NiceNIC may require authentication, confirmation, re-entry of Registration Data, payment, and other steps required or permitted by the ICANN Transfer Policy or the applicable registry.

Submission of a transfer order does not guarantee completion. A transfer may fail or be delayed because of registry status, transfer restrictions, inaccurate authorization information, dispute proceedings, security review, or other circumstances outside NiceNIC's reasonable control.

8. Change of Registrant
A change to the Registered Name Holder may be subject to the Change of Registrant provisions of the ICANN Transfer Policy, including any applicable confirmation procedure and transfer lock.

9. ccTLD and Registry-Specific Transfers
Some ccTLDs and sponsored/restricted TLDs use transfer procedures different from the ICANN Transfer Policy, including registry tokens, account identifiers, trade procedures, IPS TAG changes, local eligibility checks, or direct registry processes.

For such TLDs, the applicable registry rules control.

10. Transfer Disputes
Registrar-to-registrar disputes concerning an ICANN-governed transfer are handled under the ICANN Transfer Dispute Resolution Policy ("TDRP"). The TDRP is principally a dispute mechanism between registrars and is not a substitute for customer support, a UDRP proceeding, or court proceedings.

11. Applicable Agreements
This Policy forms part of, and should be read with:

the NiceNIC Domain Name Registration Service Agreement;
the NiceNIC Expired Domain Renewal, Redemption, and Auction Policy;
the NiceNIC Privacy Policy;
the NiceNIC Terms of Service & Acceptable Use Policy; and
applicable ICANN and registry policies.