Domain Transfer Agreement

This Domain Transfer Agreement ("Agreement") governs requests to transfer domain-name registrations through Hostwover.

This Agreement applies to:

• transfers of eligible domain names to Hostwover.
• transfers of eligible domain names away from Hostwover.
• inter-registrar transfers.
• Change of Registrant procedures where applicable.
• transfer authorization.
• transfer locks.
• transfer disputes; and
• other domain-transfer activities supported through Hostwover.

This Agreement is between:

• Hostwover ("Hostwover", "we", "us", or "our"); and
• the person or organization requesting, approving, controlling, or otherwise participating in the domain transfer ("Customer", "you", "your", "Registrant", or "Registered Name Holder", as applicable).

By submitting, authorizing, accepting, or completing a domain-transfer request through Hostwover, you agree to this Agreement.

This Agreement forms part of Hostwover's legal terms and should be read together with:

• Terms of Service.
• Registrar Information.
• Domain Registration Agreement.
• Domain Renewal & Expiration Agreement.
• Domain Expiration & Recovery Policy.
• Domain Dispute Policy.
• Privacy Policy.
• Acceptable Use Policy.
• Abuse Handling Policy.
• Refund Policy.
• Trademark & Copyright Policy.
• Complaints & Dispute Resolution; and
• applicable domain policies.

A domain transfer may also be subject to mandatory requirements imposed by:

• the Registry Operator.
• the Sponsoring Registrar.
• ICANN, where applicable.
• a competent court.
• a dispute-resolution provider; or
• applicable law.

For this Agreement:

Domain Name

The domain-name registration that is the subject of a transfer request.

Registrant

The person or organization holding the right to the applicable domain registration.

Registered Name Holder

The person or organization recognized as the holder of the registration under applicable domain records and policies.

Gaining Registrar

The registrar seeking to become responsible for sponsoring the domain registration following an inter-registrar transfer.

Losing Registrar

The registrar responsible for the registration before completion of an inter-registrar transfer.

Sponsoring Registrar

The registrar currently sponsoring the domain registration within the applicable registry.

Registry Operator

The organization operating the registry for the applicable top-level domain.

AuthInfo Code

The unique domain-transfer credential commonly referred to as an:

• Auth Code.
• EPP Code.
• Authorization Code.
• Transfer Code; or
• Transfer Secret.

Transfer Lock

A domain status or restriction that prevents or limits an inter-registrar transfer.

Change of Registrant

A material change to the person or organization recognized as the Registered Name Holder where applicable domain policy treats that change separately from an inter-registrar transfer.

Hostwover may provide functionality allowing customers to:

• initiate eligible inbound transfers.
• initiate eligible outbound transfers.
• unlock domains.
• obtain or manage AuthInfo Codes.
• authorize transfer requests.
• confirm transfer requests.
• monitor transfer status.
• cancel eligible pending transfers.
• update Registration Data.
• perform Change of Registrant procedures where supported; and
• receive domain-transfer support.

Availability depends on:

• TLD.
• Registry requirements.
• current Sponsoring Registrar.
• domain status.
• applicable policy.
• security restrictions.
• legal restrictions; and
• technical availability.

Subject to applicable restrictions, a Registered Name Holder may request transfer of an eligible domain registration from one registrar to another.

Hostwover will not impose an arbitrary restriction intended solely to prevent an otherwise valid transfer.

Transfers remain subject to:

• authorization.
• eligibility.
• security controls.
• applicable registration status.
• transfer locks.
• dispute restrictions.
• registry requirements.
• applicable ICANN policies; and
• applicable law.

To transfer an eligible domain to Hostwover, you may be required to:

1. submit the domain name.
2. unlock the domain where required.
3. obtain the applicable AuthInfo Code.
4. provide the AuthInfo Code to Hostwover.
5. pay the applicable transfer charge.
6. provide or confirm Registration Data.
7. authorize the transfer.
8. complete applicable verification; and
9. satisfy any additional requirements applicable to the domain extension.

A transfer will not be considered completed until it has been successfully processed through the applicable registration system.

Submission or payment of a transfer request does not guarantee that the transfer will succeed.

A transfer may:

• remain pending.
• require additional authorization.
• require verification.
• be rejected.
• be cancelled.
• expire.
• fail technically; or
• be prohibited by applicable domain rules.

The domain remains under its existing registration arrangement until the transfer has actually completed.

Before requesting a transfer, you are responsible for verifying that the domain is eligible.

Eligibility may depend on:

• domain age.
• date of the most recent transfer.
• domain status.
• transfer-lock status.
• expiration status.
• Registration Data.
• ownership status.
• pending disputes.
• applicable legal orders.
• verification status.
• TLD-specific requirements; and
• applicable domain policies.

For domain registrations subject to applicable ICANN Transfer Policy requirements, an inter-registrar transfer may generally be denied if requested within the first sixty (60) days after the domain's initial creation date.

Other TLDs may apply different restrictions.

The rule applicable to the particular domain controls.

For applicable domains, an inter-registrar transfer may generally be restricted during the first sixty (60) days following a previous inter-registrar transfer.

Exceptions may exist where permitted by applicable policy, dispute resolution, registrar agreement, or another authorized process.

A material Change of Registrant may trigger an inter-registrar transfer lock for applicable domains.

Where applicable ICANN rules require it, the lock may remain in effect for sixty (60) days following the Change of Registrant.

An applicable registrar may provide an option to opt out of such a lock before the Change of Registrant occurs where current policy permits that option.

An opt-out option is not guaranteed to be available.

If your objective is both to:

• transfer the domain to another registrar; and
• materially change the Registrant,

you should consider completing the inter-registrar transfer before performing the Change of Registrant where applicable.

Changing the Registrant first may trigger a transfer lock.

Hostwover is not responsible where a Customer performs a Change of Registrant that validly triggers an applicable transfer restriction.

For domain policies that recognize a Change of Registrant process, a material change may include changes to information such as:

• Registrant name.
• Registrant organization; or
• Registrant email address.

Minor typographical corrections may not necessarily constitute a material change.

Whether a change qualifies is determined according to the applicable domain policy.

A domain transfer must be authorized by a person with authority to transfer the registration.

You represent that you have authority to initiate or approve every transfer request submitted through your Hostwover Account.

You must not:

• transfer a domain you do not control.
• submit another person's AuthInfo Code without authorization.
• impersonate the Registrant.
• forge transfer approval.
• bypass transfer verification; or
• attempt to take control of another person's domain.

For applicable ICANN-governed inter-registrar transfers, the Registered Name Holder is the party with authority to approve or deny the transfer request.

Hostwover may rely on appropriate Registration Data, authorization information, Account information, or verification procedures to determine whether the transfer request is properly authorized.

A transfer may require confirmation of the Registered Name Holder's intention to transfer the domain.

Confirmation may occur through:

• email.
• Account interface.
• secure authorization workflow.
• transfer confirmation form.
• AuthInfo validation.
• electronic consent; or
• another mechanism allowed by applicable policy.

Failure to provide required authorization may prevent the transfer from proceeding.

Certain inter-registrar transfers may be subject to standardized authorization requirements under applicable ICANN Transfer Policy procedures.

Where such requirements apply, the appropriate transfer parties may be required to obtain, preserve, or process authorization evidence.

Hostwover may facilitate this process through the applicable domain-registration systems.

Many domain transfers require a unique AuthInfo Code.

The AuthInfo Code is a security credential associated with the domain.

You are responsible for protecting it against unauthorized disclosure.

Anyone who gains unauthorized access to a valid AuthInfo Code may attempt to initiate a transfer.

Where Hostwover provides access to an AuthInfo Code for an eligible domain, the code may be:

• displayed through the Account.
• generated through the Account.
• sent through an authorized secure process; or
• provided following appropriate verification.

Additional verification may be required where necessary to protect the domain.

For domains subject to applicable ICANN Transfer Policy requirements, where self-service functionality is not available, the relevant registrar may be required to provide the Registered Name Holder with the unique AuthInfo Code within the applicable policy period.

Hostwover will facilitate eligible requests according to the domain's applicable transfer procedures.

You must treat the AuthInfo Code as confidential.

You should not:

• publish it.
• place it in public messages.
• include it in screenshots shared publicly.
• send it to untrusted persons.
• store it in publicly accessible files; or
• disclose it to anyone not authorized to perform the transfer.

If you believe an AuthInfo Code has been compromised, contact Hostwover promptly.

A transfer may fail where:

• the AuthInfo Code is incorrect.
• the code has changed.
• the code has expired where applicable.
• the domain is not eligible.
• the domain remains locked; or
• another transfer requirement has not been satisfied.

You may need to obtain a new code before retrying the transfer.

Certain domains must be unlocked before transfer.

A locked domain may display a status such as:

clientTransferProhibited

or another transfer-prohibited status.

Where available, you may be able to unlock the domain through the applicable domain-management interface.

Not every domain lock can be removed immediately by the Customer.

A domain may remain locked because of:

• mandatory 60-day restrictions.
• court orders.
• pending disputes.
• UDRP proceedings.
• URS proceedings.
• security investigations.
• fraud investigations.
• ownership disputes.
• registry requirements; or
• another valid restriction.

Customers may be able to enable transfer protection or a transfer lock.

Where the lock was applied at your request or through an optional protection feature, you may need to disable that protection before transferring the domain.

Additional verification may be required for security-sensitive unlocking.

For applicable gTLDs governed by ICANN's Transfer Policy, the relevant registrar must provide a reasonable mechanism for an eligible Registered Name Holder to remove clientTransferProhibited.

Where self-service removal is unavailable, current ICANN requirements generally require applicable registrar action within five (5) calendar days of a valid request.

This does not override mandatory transfer locks or other legitimate restrictions.

Hostwover may charge a transfer fee.

The applicable charge will generally be displayed before you submit the transfer order.

Pricing may depend on:

• TLD.
• domain classification.
• currency.
• applicable taxes.
• premium status.
• registry pricing; and
• other applicable pricing factors.

Payment of a transfer fee does not guarantee transfer completion.

The transfer must still satisfy applicable authorization, eligibility, technical, registry, and policy requirements.

If a paid transfer cannot be completed, the payment will be handled according to Hostwover's Refund Policy, applicable Service terms, and mandatory law.

For certain domains, successful transfer may include an extension of the registration term.

For applicable gTLD transfers governed by the current ICANN Transfer Policy, completion of an eligible holder-authorized inter-registrar transfer generally results in a one-year extension of the existing registration term, subject to the applicable maximum registration period.

This rule does not necessarily apply to every TLD.

The Registry rules applicable to the domain control.

Some registries limit the maximum future registration period of a domain.

For applicable gTLDs, a transfer-related extension must not cause the total unexpired registration term to exceed the applicable maximum permitted period.

Where the domain is already near the maximum allowed registration term, the expected extension may be limited.

Transferring a domain close to its expiration date may create additional risk or complexity.

You should not rely on a transfer request as a substitute for timely renewal where renewal is necessary to protect the registration.

Depending on the domain:

• the domain may need to be renewed first.
• the transfer may continue.
• the transfer authorization may expire.
• the registration may enter an expired lifecycle; or
• different TLD rules may apply.

An expired domain may or may not remain transferable.

Transfer eligibility depends on:

• the domain extension.
• expiration stage.
• renewal rights.
• redemption status.
• deletion status.
• Registry rules; and
• applicable transfer policies.

Once the Registrant no longer has the right to renew or transfer the domain, a transfer may be unavailable.

Hostwover does not guarantee an exact transfer-completion time.

Processing may depend on:

• customer authorization.
• current registrar action.
• Registry processing.
• transfer policies.
• TLD rules.
• domain status.
• verification; and
• technical systems.

For applicable gTLD transfers, the current ICANN Transfer Policy provides a five-calendar-day response framework at the registry/registrar stage unless the transfer is approved, denied, or otherwise resolved earlier.

While a transfer is pending:

• the existing registrar relationship may remain active.
• DNS may continue operating.
• existing nameservers may generally remain configured.
• domain management may be restricted.
• certain Registrant changes may affect the request; and
• additional actions may invalidate or delay the transfer.

You should avoid unnecessary domain changes while an important transfer is pending.

An inter-registrar transfer does not itself normally require changing nameservers.

However, DNS availability can be affected if:

• nameservers are changed.
• DNS hosting is tied to another service.
• an external DNS service is terminated.
• the domain expires.
• DNSSEC becomes incorrectly configured; or
• the Customer changes DNS configuration.

You are responsible for ensuring continued DNS availability where configuration is under your control.

Transferring a domain to Hostwover does not automatically transfer:

• website files.
• databases.
• email messages.
• application data.
• hosting accounts.
• SSL certificates.
• server configurations; or
• other Services.

A domain transfer concerns the domain registration unless another migration Service is expressly included.

A domain transfer does not automatically migrate existing email mailboxes.

If your email is hosted elsewhere, you are responsible for preserving:

• mailbox data.
• MX records.
• SPF.
• DKIM.
• DMARC.
• user accounts; and
• other email configuration.

Transferring a domain registration does not automatically transfer or cancel an existing Google Workspace subscription.

Workspace administration and domain registration are separate unless expressly stated otherwise.

A domain transfer does not automatically change or migrate:

• VPS.
• VDS.
• servers.
• applications.
• IP addresses; or
• hosting infrastructure.

Any related DNS configuration must be maintained separately.

For applicable gTLDs, a transfer may be validly denied in circumstances recognized under the current ICANN Transfer Policy, including certain cases involving:

• evidence of fraud.
• reasonable dispute concerning the identity of the Registered Name Holder.
• qualifying unpaid registration periods.
• express objection by the authorized Registered Name Holder.
• transfer requested within the restricted period following initial registration.
• transfer requested within the restricted period following a previous inter-registrar transfer.
• pending UDRP proceedings.
• applicable court orders.
• pending transfer disputes.
• applicable URS proceedings or suspension; or
• a valid Change of Registrant transfer lock.

Other TLDs may apply different reasons.

Where required by applicable policy, the Registered Name Holder should be informed of the applicable reason when an inter-registrar transfer is denied.

Hostwover may communicate available transfer-status information through:

• the Account.
• email.
• customer support; or
• another appropriate channel.

A transfer may be denied, suspended, reversed, or investigated where there is evidence of fraud.

This may include:

• stolen credentials.
• fraudulent Account access.
• forged authorization.
• unauthorized AuthInfo use.
• payment fraud.
• identity fraud; or
• attempted domain hijacking.

A reasonable dispute concerning the identity or authority of the Registered Name Holder may prevent or delay transfer.

Hostwover may request evidence including:

• identification.
• business documents.
• registration history.
• authorization.
• Account records.
• transaction evidence.
• previous communications.
• court documents; or
• other relevant information.

An authorized Registered Name Holder may object to a transfer where applicable procedures permit.

An objection must be genuine and authorized.

No person may falsely object to another person's transfer request by impersonating the Registrant.

A transfer may be prohibited during an applicable pending Uniform Domain Name Dispute Resolution Policy ("UDRP") proceeding.

Applicable UDRP rules and decisions may also require transfer, cancellation, lock, or another action concerning the domain.

A pending Uniform Rapid Suspension System ("URS") proceeding or applicable URS suspension may restrict transfer of certain domains.

Hostwover will implement applicable requirements where required.

A transfer may be prohibited, delayed, reversed, or otherwise affected by a valid order from a court with appropriate jurisdiction.

Hostwover may request verification of the legal order before taking action.

Disputes relating to an inter-registrar transfer may be subject to applicable transfer-dispute procedures.

For eligible gTLDs, this may include procedures associated with the ICANN Transfer Dispute Resolution Policy ("TDRP").

The TDRP primarily governs disputes between registrars concerning whether an inter-registrar transfer was handled in accordance with applicable policy.

If you believe your domain was transferred without authorization, you must contact Hostwover or the appropriate registrar involved as soon as possible.

Provide available evidence concerning:

• prior ownership.
• previous registrar.
• Account access.
• transfer notifications.
• Registration Data.
• suspected compromise; and
• relevant dates.

Prompt reporting may improve the possibility of investigation or recovery.

A completed transfer may be reversed where authorized by applicable domain policies.

Circumstances may include:

• agreement between appropriate registrars that the transfer was erroneous.
• a binding transfer-dispute decision.
• a court order.
• evidence supporting an authorized reversal mechanism; or
• another applicable Registry process.

Hostwover cannot guarantee that every unauthorized transfer can be reversed.

Domain hijacking is an unauthorized takeover or transfer of domain control.

You must immediately report suspected:

• Account compromise.
• unauthorized transfer.
• unauthorized Registrant change.
• AuthInfo theft.
• unauthorized domain unlock.
• unauthorized nameserver changes; or
• suspicious transfer notifications.

Hostwover may temporarily restrict domain actions while investigating.

Hostwover may use security controls relating to transfers including:

• Account authentication.
• MFA where available.
• transfer locks.
• AuthInfo Codes.
• additional verification.
• activity monitoring.
• fraud detection.
• ownership verification.
• email confirmation; and
• security holds.

Security measures may vary according to the risk associated with the request.

Hostwover may require additional verification before:

• releasing sensitive transfer credentials.
• unlocking a protected domain.
• approving a high-risk transfer.
• changing Registrant information.
• processing a disputed transfer; or
• assisting with suspected domain hijacking.

The requested verification should be proportionate to the relevant security risk.

You are responsible for protecting your Hostwover Account.

You should:

• use a strong unique password.
• enable available MFA.
• protect your email account.
• protect recovery methods.
• protect AuthInfo Codes.
• monitor Account activity; and
• report unauthorized access promptly.

The email address associated with your domain registration may be used for transfer-related authorization or notifications.

Compromise of that email account can create a significant domain-security risk.

You should protect it using:

• a unique password.
• MFA where available.
• secure recovery methods; and
• appropriate monitoring.

Inaccurate or inaccessible Registration Data may delay or prevent a transfer where it interferes with:

• authorization.
• verification.
• ownership validation; or
• applicable domain requirements.

You are responsible for maintaining accurate Registration Data.

Changing Registration Data immediately before an intended inter-registrar transfer may affect transfer eligibility.

In particular, certain material Registrant changes may trigger a transfer lock.

Customers planning both a transfer and a Registrant update should consider the order of those actions carefully.

Following completion of a transfer, Registration Data may be:

• re-confirmed.
• re-entered.
• updated.
• validated; or
• processed

according to applicable Registration Data rules.

You remain responsible for ensuring the information is accurate.

Transfer-related Personal Data will be processed according to:

• Hostwover's Privacy Policy.
• applicable data-protection law.
• Registry requirements.
• applicable domain policies; and
• applicable Registration Data requirements.

For applicable gTLDs, the ICANN Registration Data Policy has been effective since August 21, 2025.

Hostwover or applicable domain-system participants may retain transfer-related records where required for:

• authorization evidence.
• security.
• fraud prevention.
• dispute resolution.
• legal compliance.
• Registry requirements.
• ICANN requirements; or
• recordkeeping obligations.

Such records may include:

• transfer request.
• authorization.
• transfer status.
• AuthInfo-related events.
• Account identifiers.
• Registration Data.
• verification.
• timestamps; and
• communications.

Following successful transfer to Hostwover, management of the domain through Hostwover will also be subject to the applicable:

• Domain Registration Agreement.
• Domain Renewal & Expiration Agreement.
• Registrar Information.
• Terms of Service; and
• other applicable policies.

After successful transfer, future renewals will be governed by Hostwover's applicable renewal pricing and Domain Renewal & Expiration Agreement.

The price charged for the transfer does not guarantee the same amount for future renewals.

Hostwover may occasionally offer discounted transfer pricing.

Promotional transfer prices may:

• apply only to certain TLDs.
• apply for a limited time.
• apply only to eligible domains.
• exclude premium domains.
• have quantity limits; or
• include other disclosed conditions.

A promotional transfer price does not guarantee promotional renewal pricing.

Premium domains may have different:

• transfer pricing.
• renewal pricing.
• eligibility requirements.
• restoration pricing; or
• transfer procedures.

Hostwover may require additional confirmation where premium pricing is identified during transfer processing.

Not every domain extension is transferable through Hostwover.

A domain may be unavailable for transfer because:

• Hostwover does not support the TLD.
• technical transfer support is unavailable.
• Registry restrictions apply.
• eligibility requirements cannot be satisfied; or
• another Service limitation exists.

Country-code top-level domains may use transfer procedures significantly different from gTLD procedures.

A ccTLD transfer may require:

• special authorization.
• Registrant documentation.
• local presence.
• specific Registry forms.
• direct Registry approval.
• different transfer codes.
• different transfer periods; or
• other Registry-specific procedures.

ICANN's general gTLD Transfer Policy should not be assumed to govern every ccTLD.

Although certain successful inter-registrar transfers extend the registration term, this is not universal.

Some TLDs may:

• provide no extension.
• use a different extension period.
• impose special transfer rules; or
• treat transfers differently.

The applicable Registry policy determines the result.

Subject to applicable restrictions, you may request transfer of an eligible domain away from Hostwover.

Hostwover will not prevent a valid transfer merely because you have chosen another domain-management provider.

You remain responsible for completing the transfer process correctly.

An outbound transfer may require you to:

1. verify that the domain is eligible.
2. ensure the Registrant information is correct.
3. remove eligible transfer locks.
4. obtain the AuthInfo Code.
5. initiate the transfer with the destination service.
6. respond to authorization requests; and
7. monitor the transfer until completion.

Where your domain is subject only to a removable customer-controlled transfer lock, you may request or perform an unlock using available functionality.

A mandatory policy, court, security, dispute, or Registry lock may not be removable merely because you request an outbound transfer.

A transfer must not be used improperly as a payment-collection mechanism.

However, applicable transfer policy may permit denial in limited circumstances involving unpaid prior or current registration periods.

Independent unpaid Hostwover Services remain payable even where the domain is successfully transferred away.

Completing an outbound domain transfer does not cancel charges validly incurred before the transfer.

This may include:

• registration charges.
• renewal charges.
• restoration charges.
• other Services.
• invoices; or
• legally payable amounts.

An outbound domain transfer does not automatically terminate:

• Web Hosting.
• VPS.
• VDS.
• Professional Email.
• Google Workspace.
• SSL.
• backups.
• or other Hostwover Services.

You must cancel or modify those Services separately where desired.

Existing nameservers may remain assigned following a transfer, but Hostwover does not guarantee continued availability of DNS infrastructure tied to a Service that you cancel.

Before terminating related Services, ensure that necessary DNS records and nameserver arrangements have been migrated.

A pending transfer may be cancellable only while the applicable transfer process permits cancellation.

After a transfer is completed, it generally cannot simply be cancelled.

A new transfer or authorized reversal procedure may instead be required.

Hostwover is not responsible for transfer failure caused solely by Customer-controlled errors such as:

• incorrect AuthInfo Code.
• failure to unlock the domain.
• failure to authorize.
• incorrect domain name.
• inaccessible Registrant email.
• performing a Change of Registrant immediately before transfer.
• failure to meet eligibility requirements; or
• Customer cancellation.

Mandatory rights remain unaffected.

Hostwover may display transfer statuses such as:

• Pending.
• Awaiting Authorization.
• Processing.
• Action Required.
• Transfer Locked.
• Failed.
• Cancelled.
• Rejected; or
• Completed.

Status terminology may vary depending on the systems involved.

Hostwover may send transfer-related communications concerning:

• transfer initiation.
• authorization.
• status changes.
• AuthInfo requests.
• security warnings.
• failure.
• cancellation.
• completion.
• Change of Registrant.
• transfer locks; or
• suspected unauthorized activity.

These are operational communications and are separate from optional marketing.

If you believe an eligible transfer was improperly denied, contact Hostwover Support.

Where the issue involves another registrar or Registry, Hostwover may:

• review the information available to us.
• explain the known status.
• identify missing requirements.
• submit an appropriate request.
• coordinate through applicable domain channels; or
• direct you to an appropriate formal procedure.

Hostwover cannot guarantee the outcome of a dispute controlled by another authorized domain-system participant.

When reporting an unauthorized transfer, you should provide as much relevant information as possible.

This may include:

• domain name.
• Hostwover Account.
• previous Registrant information.
• previous registrar.
• transfer date.
• suspicious emails.
• security alerts.
• login information.
• proof of prior control; and
• a description of what occurred.

Do not send unnecessary passwords, private keys, or complete payment-card information.

Where applicable, disputes between registrars concerning an alleged invalid or improperly denied inter-registrar transfer may be handled under the applicable Transfer Dispute Resolution Policy.

Customer complaints may also be subject to Hostwover's Complaints & Dispute Resolution procedures.

A transfer dispute and a legal domain-ownership dispute are not necessarily the same.

Ownership disputes may require:

• UDRP.
• URS.
• a ccTLD dispute procedure.
• trademark proceedings.
• court proceedings; or
• another binding dispute-resolution mechanism.

Hostwover does not act as a court or trademark tribunal.

A Registry Operator may perform or require actions affecting a domain transfer.

Hostwover cannot override a binding Registry action.

Such action may include:

• rejection.
• lock.
• reversal.
• administrative transfer.
• policy enforcement; or
• another authorized registry action.

In certain exceptional circumstances, domain registrations may be transferred through an ICANN-approved or Registry-administered process rather than an ordinary customer-requested transfer.

Such transfers may arise in circumstances involving registrar transition, accreditation issues, acquisitions, or other authorized bulk-transfer processes.

These transfers may follow different procedures from ordinary inter-registrar transfers.

Domain transfer requirements may change over time.

Changes may result from:

• ICANN policy development.
• Registry policy.
• technical standards.
• legal requirements.
• security requirements; or
• other binding domain-system changes.

Hostwover may update its transfer procedures when necessary to implement those requirements.

The transfer rules in effect when a transfer is processed may apply even if they differ from the rules that existed when the domain was originally registered.

Hostwover cannot guarantee that transfer procedures will remain unchanged for the entire lifecycle of a domain.

A domain involved in a credible abuse, fraud, security, or ownership investigation may be temporarily restricted where permitted or required.

Restrictions must be reasonably related to the relevant risk or applicable legal requirement.

Hostwover will not arbitrarily seize or permanently prevent transfer of a domain without an applicable contractual, security, policy, or legal basis.

Hostwover may restrict, preserve, reverse, or otherwise take action concerning a transfer where required by a valid:

• court order.
• regulatory instruction.
• law-enforcement requirement.
• Registry directive.
• dispute decision; or
• other binding legal requirement.

By requesting a transfer, you represent that:

• you have authority to request it.
• the transfer is not fraudulent.
• the AuthInfo Code was lawfully obtained.
• information you provide is accurate.
• you are not unlawfully attempting to take another person's domain.
• you will complete applicable verification; and
• you will comply with applicable transfer policies.

You must not:

• attempt domain hijacking.
• steal AuthInfo Codes.
• forge authorization.
• impersonate a Registrant.
• manipulate Registration Data to obtain a domain.
• bypass security controls.
• submit fraudulent documents.
• use compromised Accounts to transfer domains; or
• knowingly participate in an unauthorized transfer.

Such activity may result in:

• transfer cancellation.
• Account restriction.
• Service suspension.
• investigation.
• preservation of evidence; or
• legal action.

Hostwover's liability concerning domain transfers is subject to the limitation-of-liability provisions in the Terms of Service.

To the maximum extent permitted by applicable law, Hostwover is not responsible for losses caused solely by:

• unauthorized disclosure of Customer-controlled AuthInfo Codes.
• compromise of Customer-controlled email.
• Customer failure to complete authorization.
• Customer-requested Change of Registrant locks.
• Customer-controlled DNS changes.
• invalid Registration Data supplied by the Customer.
• a mandatory Registry restriction.
• an applicable policy restriction; or
• a binding legal action.

Nothing in this Agreement excludes liability that cannot lawfully be excluded.

Hostwover cannot guarantee recovery of a domain following an unauthorized completed transfer.

The availability of recovery depends on:

• the facts.
• timing.
• applicable transfer policy.
• registrar cooperation.
• Registry mechanisms.
• evidence.
• dispute procedures; and
• legal remedies.

You should report suspected unauthorized transfers immediately.

To the maximum extent permitted by applicable law, you agree to indemnify Hostwover against third-party claims, liabilities, damages, and reasonable costs arising directly from:

• a fraudulent transfer submitted by you.
• unauthorized transfer activity performed by you.
• forged authorization.
• violation of another person's domain rights.
• intentional misuse of transfer systems; or
• material breach of this Agreement.

This does not apply to the extent the claim results from Hostwover's own conduct for which Hostwover is legally responsible.

Mandatory consumer rights remain unaffected.

Transfer fees are governed by Hostwover's Refund Policy.

A transfer fee may be refundable where:

• the transfer cannot be submitted.
• the transaction fails before completion.
• Hostwover expressly provides a refund.
• the relevant transaction can be reversed; or
• applicable law requires a refund.

A successfully completed domain transfer may be irreversible and therefore generally non-refundable except where applicable law or Hostwover's Refund Policy provides otherwise.

A transfer failing does not automatically determine the refund outcome.

For example, treatment may differ where failure resulted from:

• technical failure.
• unsupported domain.
• incorrect Customer AuthInfo Code.
• Customer cancellation.
• transfer lock.
• Registry rejection.
• failure to authorize; or
• another reason.

Hostwover will apply the Refund Policy and applicable law.

Subject to mandatory consumer protections and domain-specific requirements, this Agreement is governed by the law specified in Hostwover's Terms of Service.

Where the Terms of Service specify the laws of the Arab Republic of Egypt, the same governing law applies to this Agreement unless a mandatory domain policy or applicable law requires otherwise.

Nothing in the general governing-law clause replaces mandatory domain-specific procedures that may apply.

A domain may separately be subject to:

• ICANN Transfer Policy.
• TDRP.
• UDRP.
• URS.
• Registry dispute procedures.
• ccTLD dispute procedures; or
• applicable court orders.

If you believe Hostwover has incorrectly handled your transfer request, contact Hostwover Support so we can investigate.

You may also use Hostwover's:

Complaints & Dispute Resolution

process.

Nothing in this Agreement prevents you from exercising any mandatory complaint right available under applicable law or domain policy.

You should retain information reasonably necessary to demonstrate your rights relating to important domains.

This may include:

• registration confirmation.
• original registration date.
• invoices.
• historical Registration Data.
• transfer confirmations.
• ownership documentation; and
• relevant authorization records.

Maintaining appropriate records can assist with future ownership or transfer disputes.

Hostwover may update this Agreement to reflect:

• changes to Domain Services.
• ICANN policy changes.
• Registry policy changes.
• transfer-process changes.
• security improvements.
• changes to Registration Data requirements.
• legal developments; or
• clarification of existing terms.

The latest published version will display an updated Last Updated date.

Where applicable law requires notice concerning a material contractual change, Hostwover may provide notice through:

• email.
• Account notification.
• website notice; or
• another appropriate method.

Where explicit acceptance is legally required, Hostwover will seek that acceptance.

A mandatory change in:

• law.
• ICANN policy.
• Registry requirements.
• domain-dispute procedures; or
• another binding domain requirement

may apply to existing domains even where the change occurred after the original registration.

If a provision of this Agreement conflicts with a mandatory transfer requirement, the mandatory requirement controls to the extent of the conflict.

Relevant requirements may include:

1. applicable law.
2. court orders.
3. applicable ICANN Transfer Policy.
4. Registry policies.
5. Sponsoring Registrar requirements.
6. applicable dispute-resolution decisions; and
7. other binding domain requirements.

If any provision of this Agreement is determined to be invalid or unenforceable, the remaining provisions remain effective to the maximum extent permitted by law.

Failure to enforce a provision immediately does not constitute a permanent waiver of the right to enforce that provision later.

This Agreement may be accepted electronically.

Hostwover may maintain records relating to acceptance, including:

• Account.
• Agreement version.
• acceptance timestamp.
• order.
• domain name.
• IP information; and
• relevant transaction information.

Customers transferring domains should review:

• Terms of Service
• Registrar Information
• Domain Registration Agreement
• Domain Renewal & Expiration Agreement
• Domain Expiration & Recovery Policy
• Domain Dispute Policy
• Privacy Policy
• Acceptable Use Policy
• Abuse Handling Policy
• Refund Policy
• Trademark & Copyright Policy
• Complaints & Dispute Resolution

For assistance with a domain transfer:

Hostwover Support

Website: hostwover.com

Email: [email protected]

Where appropriate, include:

• domain name.
• Hostwover Account email.
• transfer order number.
• current transfer status.
• relevant error message; and
• description of the issue.

Do not send:

• your Hostwover password.
• MFA recovery codes.
• private keys.
• complete payment-card information.
• CVV.
• unrelated API credentials; or
• unrelated sensitive information

through ordinary support communications.

Where an AuthInfo Code is required for troubleshooting, use only an authorized secure method provided for that purpose.

By requesting or participating in a domain transfer through Hostwover, you acknowledge that domain transfers involve authorization, security controls, Registry processing, applicable domain policies, and potentially multiple domain-system participants.

Hostwover will seek to provide a clear and secure transfer process and will not knowingly prevent an otherwise valid transfer without an appropriate contractual, security, policy, or legal basis.

You remain responsible for:

• ensuring that you have authority over the domain.
• protecting your Hostwover Account.
• protecting your Registrant email.
• protecting AuthInfo Codes.
• ensuring Registration Data is accurate.
• reviewing transfer locks before making Registrant changes.
• completing required authorization.
• monitoring the transfer until completion; and
• promptly reporting suspected unauthorized activity.