Domain Dispute Policy

The purpose of this Policy is to explain:

• Hostwover's role in domain disputes.
• which disputes Hostwover may handle directly.
• which disputes must be referred to another authority.
• how trademark-based domain disputes are handled.
• how UDRP and URS proceedings affect a domain.
• how ownership disputes are treated.
• how transfer disputes are handled.
• how court orders and legal proceedings are handled.
• when a domain may be locked or restricted.
• how Customers should respond to disputes; and
• when Hostwover may escalate a matter to the sponsoring registrar or registry.

This Policy may apply to disputes involving:

• domain registration.
• domain ownership.
• registrant identity.
• domain transfers.
• change of registrant.
• unauthorized transfers.
• alleged domain hijacking.
• trademark claims.
• cybersquatting allegations.
• UDRP proceedings.
• URS proceedings.
• registry-specific disputes.
• country-code domain disputes.
• court orders.
• arbitration proceedings.
• registrar transfer disputes; and
• other disputes affecting control or status of a domain name.

Hostwover provides domain-registration and related services to Customers.

Depending on the domain extension and applicable supply arrangement, Hostwover may provide the domain through an upstream:

• ICANN-accredited registrar.
• registry-integrated registrar.
• domain reseller platform.
• registry service provider; or
• other authorized domain-services provider.

Hostwover is not necessarily the registrar of record for a domain purchased through Hostwover.

The Sponsoring Registrar is the registrar shown as responsible for the domain registration in the applicable registration-data system.

Certain actions involving a disputed domain may only be performed by the Sponsoring Registrar or applicable registry.

Hostwover may therefore need to escalate or forward requests to the Sponsoring Registrar.

Hostwover does not act as:

• a court.
• an arbitration tribunal.
• a trademark tribunal.
• a UDRP panel.
• a URS examiner; or
• an independent adjudicator of competing ownership claims.

Except where required by an applicable policy, provider requirement, or legally binding order, Hostwover will not decide which competing party has superior legal ownership rights to a domain.

A complaint stating that a person:

• owns a trademark.
• owns a business name.
• previously used a domain.
• paid for a domain.
• has a contractual right to a domain; or
• believes a domain should belong to them

does not by itself require Hostwover to transfer the domain to that person.

Appropriate evidence or a recognized legal or dispute-resolution process may be required.

A disputed domain may be subject to one or more external dispute procedures depending on:

• the domain extension.
• applicable registrar.
• registry.
• registration agreement.
• location of the parties.
• nature of the dispute; and
• applicable law.

These procedures may include:

• Uniform Domain Name Dispute Resolution Policy ("UDRP").
• Uniform Rapid Suspension System ("URS").
• registry-specific dispute procedures.
• country-code dispute procedures.
• Registrar Transfer Dispute Resolution procedures.
• court proceedings.
• arbitration; or
• another recognized dispute mechanism.

Where applicable to a domain registration, the Uniform Domain Name Dispute Resolution Policy ("UDRP") forms part of the domain's applicable registration framework.

UDRP proceedings are administered by ICANN-approved dispute-resolution service providers rather than Hostwover.

Hostwover does not decide the outcome of a UDRP complaint.

Under the UDRP, a complainant generally must establish that:

1. the disputed domain is identical or confusingly similar to a trademark or service mark in which the complainant has rights.
2. the registrant has no rights or legitimate interests in the domain; and
3. the domain was registered and is being used in bad faith.

The complainant must establish the required elements under the applicable UDRP procedure.

Hostwover will not ordinarily determine whether:

• a domain is confusingly similar to a trademark.
• a registrant has legitimate interests.
• registration occurred in bad faith.
• use constitutes bad faith.
• a trademark is legally enforceable; or
• a complainant has satisfied the UDRP burden.

These questions are for the appropriate dispute-resolution panel.

A party seeking relief under the UDRP must submit its complaint to an appropriate ICANN-approved UDRP dispute-resolution provider.

Sending a trademark complaint only to Hostwover does not commence a UDRP proceeding.

UDRP proceedings are administered by dispute-resolution service providers approved for that purpose under the ICANN framework.

The selected provider's applicable:

• rules.
• supplemental rules.
• filing requirements.
• deadlines.
• fees; and
• procedures

will apply to the proceeding.

ICANN's UDRP Rules define a Provider as an ICANN-approved dispute-resolution service provider.

When a valid UDRP proceeding is initiated, the applicable UDRP provider may seek verification information from the registrar.

Where Hostwover is not the registrar of record, Hostwover may cooperate with or forward relevant communications to the Sponsoring Registrar.

A domain subject to a UDRP proceeding may be placed under an applicable dispute lock.

Under the UDRP Rules, the lock is intended at minimum to prevent modification of registrant and registrar information by the respondent while the proceeding is pending, while not preventing the domain from resolving or being renewed merely because of that lock.

Hostwover may assist the Sponsoring Registrar with implementation where necessary.

A UDRP or dispute lock is an administrative protection.

It does not mean that:

• the complainant has won.
• the registrant has lost.
• infringement has been established.
• ownership has transferred; or
• Hostwover has made a legal determination.

During a recognized domain-dispute proceeding, Hostwover may restrict actions that would improperly alter the status of the disputed registration.

This may include restrictions on:

• changing the registrant.
• transferring the domain.
• moving the domain between accounts.
• disabling a dispute lock; or
• making another change prohibited by the applicable dispute procedure.

The UDRP expressly contains status-quo and transfer restrictions during applicable proceedings.

A Customer receiving notice of a UDRP complaint is responsible for:

• reviewing the complaint.
• monitoring deadlines.
• responding through the dispute provider.
• obtaining legal advice if desired.
• maintaining accurate contact information; and
• complying with the applicable proceeding.

Hostwover does not prepare the Customer's UDRP defense.

Failure to respond to a UDRP proceeding may affect the registrant's ability to defend the registration.

Hostwover is not responsible for a Customer's failure to:

• monitor correspondence.
• respond to the provider.
• meet deadlines; or
• submit relevant evidence.

Where a UDRP panel issues a binding administrative decision requiring action concerning the domain, the Sponsoring Registrar may implement the applicable remedy in accordance with the UDRP and its Rules.

Hostwover may cooperate with that implementation.

Hostwover does not award monetary damages in connection with UDRP proceedings.

Any monetary, contractual, tort, or other legal claims must be pursued through the appropriate legal process.

The UDRP preserves a mechanism through which a losing registrant may commence qualifying court proceedings before implementation of certain transfer or cancellation decisions.

Under the current UDRP, the registrar waits the specified 10 business-day period following notice of the decision before implementing an applicable transfer or cancellation, and timely qualifying court documentation may prevent implementation while the court matter remains unresolved.

Hostwover will cooperate with the Sponsoring Registrar where such circumstances apply.

Hostwover does not:

• prepare court filings.
• select a court.
• determine jurisdiction.
• represent the Customer.
• provide litigation strategy; or
• guarantee that a court filing satisfies UDRP requirements.

Customers should seek qualified legal advice where necessary.

The UDRP Rules recognize Reverse Domain Name Hijacking as bad-faith use of the UDRP process to attempt to deprive a registered domain holder of a domain.

Whether conduct constitutes Reverse Domain Name Hijacking is determined by the applicable UDRP panel, not Hostwover.

Certain domains may also be subject to the Uniform Rapid Suspension System ("URS").

URS is a separate rights-protection mechanism intended to complement the UDRP in qualifying clear-cut infringement cases.

A URS complaint must be handled through an applicable approved URS provider.

Hostwover does not act as the URS examiner and does not independently decide whether the complainant has satisfied the URS requirements.

When Hostwover or the Sponsoring Registrar receives proper notice of an applicable URS proceeding, the domain may become subject to restrictions required by the URS procedure.

Hostwover may cooperate with the registrar, registry, and URS provider in implementing those requirements.

The ICANN Transfer Policy requires a registrar that has been informed of an applicable pending URS proceeding or URS suspension to deny an inter-registrar transfer while the applicable condition exists.

Hostwover may therefore be unable to process an otherwise valid transfer request.

The ICANN Transfer Policy similarly requires denial of an inter-registrar transfer when the registrar has been informed of a pending UDRP proceeding.

The UDRP restricts transfer of the disputed registration to another holder during a pending UDRP proceeding and for the period specified by the applicable policy after the proceeding concludes.

Hostwover will not knowingly facilitate a transfer intended to evade those restrictions.

A disputed registration may not be transferred to another registrar during a pending UDRP proceeding or during the post-proceeding restricted period established by the UDRP.

Country-code top-level domains ("ccTLDs") may use dispute-resolution procedures different from the UDRP or URS.

Examples of the rules that may vary include:

• eligible complaints.
• evidence requirements.
• filing providers.
• appeal rights.
• transfer restrictions.
• remedies.
• deadlines; and
• fees.

The applicable registry policy controls.

Some domain extensions may have their own:

• eligibility rules.
• nexus requirements.
• rights-protection procedures.
• trademark policies.
• reserved-name policies.
• abuse policies; or
• dispute procedures.

Customers agree to comply with the rules applicable to the selected extension.

A registry, registrar, ICANN, dispute-resolution provider, or other appropriate authority may modify an applicable dispute procedure from time to time.

The version legally applicable to the relevant dispute will govern.

Hostwover may receive complaints alleging that a domain infringes a:

• registered trademark.
• unregistered trademark.
• trade name.
• business name.
• brand.
• service mark; or
• similar right.

Receipt of such a complaint does not automatically require suspension or transfer of the domain.

Ownership of a trademark does not by itself authorize Hostwover to transfer a registered domain to the trademark owner.

Trademark/domain disputes may require resolution through:

• UDRP.
• URS where applicable.
• court proceedings.
• settlement; or
• another applicable dispute procedure.

Hostwover may receive cease-and-desist letters or similar notices.

Unless a notice creates an independent legal obligation for Hostwover, receipt of a private demand letter does not automatically require Hostwover to:

• transfer a domain.
• suspend a domain.
• delete a domain.
• disclose Customer information; or
• decide the legal dispute.

Hostwover may forward a domain-related complaint to:

• the registrant.
• Customer.
• Sponsoring Registrar.
• registry.
• upstream provider.
• dispute-resolution provider; or
• another appropriate party

where reasonably necessary.

A Customer receiving a forwarded complaint should independently determine whether to:

• respond.
• seek legal advice.
• negotiate.
• defend the registration.
• modify use of the domain; or
• participate in an applicable dispute procedure.

Hostwover does not negotiate legal settlements on behalf of Customers.

Hostwover may receive disputes between persons who both claim ownership or control of the same domain.

Examples may include disputes between:

• business partners.
• employers and employees.
• companies and developers.
• agencies and clients.
• former directors.
• shareholders.
• family members.
• buyers and sellers.
• organizations and former administrators; or
• other competing claimants.

Hostwover may consider applicable registrar or registry records when determining who is currently recorded as the registrant or authorized domain holder.

However, registration records do not prevent another party from asserting legal ownership through an appropriate legal proceeding.

The person who controls a Hostwover account is not necessarily the same person or entity legally recorded as the domain registrant.

Where ownership is disputed, Hostwover may consider:

• registration records.
• account history.
• payment records.
• communications.
• authorization records.
• transfer records.
• organization information.
• verification evidence; and
• applicable provider information.

Payment for a domain does not necessarily establish legal ownership of that domain.

For example, a:

• developer.
• employee.
• accountant.
• agency.
• reseller.
• contractor; or
• business partner

may pay for a domain on behalf of another person or organization.

Hostwover will not decide a complex ownership dispute solely by determining who made a payment.

Possession of:

• a password.
• account login.
• email account.
• API key.
• authentication device; or
• other credential

does not by itself conclusively establish legal ownership of a disputed domain.

Hostwover generally will not adjudicate internal disputes concerning:

• corporate ownership.
• partnership rights.
• employment relationships.
• shareholder rights.
• director authority.
• agency relationships; or
• contractual ownership.

Parties may be required to resolve such disputes through agreement, arbitration, or court proceedings.

A former employee, developer, contractor, agency, or administrator does not automatically retain rights to a domain merely because that person originally created or managed the Hostwover account.

Likewise, an employer or client does not automatically obtain control merely by making an unsupported ownership claim.

Hostwover may require appropriate evidence or legal determination.

Where a domain is registered for a company or organization, Hostwover may request evidence demonstrating that a person requesting a sensitive change is authorized to act for that entity.

Evidence may depend on the circumstances.

Where a registrant is deceased, Hostwover may require appropriate documentation before assisting with control or ownership changes.

Documentation may include evidence establishing:

• the registrant's death.
• identity of the requester.
• legal authority over the estate; and
• entitlement to request the domain change.

Requirements may also depend on the Sponsoring Registrar.

Disputes arising from private domain sales between third parties are primarily disputes between the buyer and seller.

Unless Hostwover expressly provided an escrow or brokerage service, Hostwover does not guarantee:

• payment.
• transfer completion.
• seller authority.
• buyer performance; or
• enforcement of private sale agreements.

If a Customer believes a domain was moved, modified, transferred, or reassigned without authorization, the Customer should contact Hostwover promptly.

Hostwover may initiate a security investigation.

Suspected domain hijacking may involve:

• stolen credentials.
• compromised email.
• unauthorized account access.
• fraudulent transfer.
• unauthorized change of registrant; or
• social engineering.

Such matters may be handled under both this Policy and applicable account-security procedures.

Where Hostwover reasonably suspects an active domain takeover, Hostwover may temporarily restrict certain account or domain actions while the issue is investigated.

Such restrictions are protective and do not constitute a final ownership determination.

Hostwover may require identity or authorization verification before making changes to a disputed domain.

Verification may include appropriate evidence concerning:

• identity.
• organization.
• account control.
• registration history.
• payment information.
• domain control.
• previous communications; and
• authorization.

Hostwover will not ordinarily transfer a disputed domain from one Customer to another solely because one party submits a support request claiming ownership.

Where competing parties reach a settlement, Hostwover may implement an agreed domain change where:

• the request is properly authenticated.
• both necessary parties have provided required authorization.
• the domain is not subject to a conflicting lock or proceeding.
• the Sponsoring Registrar permits the change; and
• applicable requirements are satisfied.

Hostwover may request reasonable documentation confirming a settlement before taking action on a disputed domain.

Hostwover will review legally valid court orders concerning domains supplied through Hostwover.

A court order may need to be implemented by the Sponsoring Registrar or registry rather than Hostwover directly.

Hostwover may verify that an order appears to originate from an appropriate court or legally competent authority before acting.

Hostwover reserves the right to seek legal advice regarding:

• validity.
• scope.
• authenticity.
• jurisdiction.
• interpretation; or
• enforceability

of an order.

Under the applicable ICANN Transfer Policy, a registrar that has been informed of a qualifying court order from a court of competent jurisdiction must deny an inter-registrar transfer where required by that policy.

Ordinary Customer Support is not necessarily authorized to accept formal legal service on behalf of:

• a Customer.
• registrant.
• registrar.
• registry; or
• another third party.

Legal documents should be served through the legally appropriate channel.

Parties should not name Hostwover in a private domain dispute merely because Hostwover supplies domain-management services.

Where Hostwover is unnecessarily named in litigation or another proceeding, Hostwover reserves all applicable rights and defenses.

The UDRP similarly states that the registrar is not intended to participate in disputes between the registrant and third parties concerning the registration and use of the domain.

Hostwover may recognize an arbitration decision affecting a domain where:

• the parties are properly bound by the arbitration.
• the decision is valid and enforceable.
• Hostwover or the Sponsoring Registrar is required or authorized to act; and
• no conflicting legal restriction prevents implementation.

Disputes concerning an inter-registrar transfer may be governed by the applicable ICANN Transfer Policy or Transfer Dispute Resolution procedure.

Hostwover may assist with gathering information and escalating the matter to the Sponsoring Registrar.

ICANN maintains a process addressing certain disputes between registrars concerning inter-registrar transfers.

The process is principally a registrar-level mechanism rather than a substitute for every Customer ownership dispute.

If a Customer believes a transfer occurred without authorization, the Customer must notify Hostwover as soon as reasonably possible.

Delay may make investigation or reversal more difficult.

Hostwover or the Sponsoring Registrar may review evidence such as:

• transfer authorization records.
• authentication records.
• timestamps.
• registration data.
• account-access records.
• communication history.
• transfer codes.
• confirmation messages; and
• registrar records.

A domain may be subject to transfer restrictions for reasons independent of a dispute.

Examples include applicable restrictions following:

• initial registration.
• inter-registrar transfer.
• Change of Registrant; or
• a Customer-enabled lock.

The applicable ICANN Transfer Policy currently recognizes, among other things, transfer restrictions within the specified periods after initial registration, a registrar transfer, and certain Changes of Registrant.

Separate transfer restrictions may apply because of:

• UDRP.
• URS.
• court order; or
• a pending transfer dispute.

These restrictions may override an ordinary Customer request to unlock or transfer the domain.

Hostwover cannot remove a lock where the Sponsoring Registrar, registry, dispute provider, applicable policy, or binding legal order requires the lock to remain.

Hostwover may refuse or delay a Change of Registrant where the change would conflict with:

• UDRP.
• URS.
• court proceedings.
• transfer-dispute procedures.
• registrar requirements.
• registry requirements; or
• another applicable restriction.

A domain dispute does not automatically renew the domain.

The Customer remains responsible for applicable renewal obligations unless the Sponsoring Registrar or dispute procedure provides otherwise.

A UDRP lock itself is defined so that it does not prevent renewal of the domain.

A Customer defending a domain dispute should generally continue to monitor:

• expiration dates.
• renewal invoices.
• payment methods.
• registration status; and
• registrar communications.

Hostwover is not responsible for loss resulting from a Customer intentionally or negligently allowing a disputed domain to expire where applicable rules permit expiration.

If a disputed domain approaches expiration, handling may depend on the:

• applicable dispute procedure.
• registrar.
• registry.
• domain extension; and
• status of the proceeding.

Hostwover may seek instructions from or coordinate with the Sponsoring Registrar.

Hostwover may refuse to process a voluntary cancellation request where cancellation would conflict with a pending dispute, lock, legal order, or provider requirement.

Whether DNS or nameserver changes are permitted during a dispute depends on the applicable lock and provider requirements.

Hostwover may restrict changes where necessary to preserve the status of the domain or comply with a dispute process.

A domain dispute and a website-content complaint are not necessarily the same matter.

A UDRP or ownership dispute concerns rights relating to the domain registration.

Separate content may be handled under:

• Acceptable Use Policy.
• Abuse Handling Policy.
• hosting terms; or
• applicable law.

Phishing, malware, botnet activity, pharming, and similar DNS abuse may require security mitigation even if no ownership dispute exists.

Such matters should primarily be handled through the Hostwover Abuse Handling Policy.

Even where Hostwover suspends or mitigates an abusive domain, the reporting party does not automatically acquire ownership of that domain.

Copyright infringement involving content hosted at a domain does not ordinarily establish ownership rights to the domain itself.

Content complaints and domain ownership claims may therefore be handled separately.

Hostwover does not treat every dispute concerning:

• defamation.
• criticism.
• reviews.
• commercial disagreements.
• political speech.
• contract disputes; or
• website content

as a domain-ownership dispute.

Appropriate legal procedures may be required.

Use of privacy or proxy registration services does not eliminate a registrant's responsibility under applicable dispute procedures.

Where legally and contractually appropriate, information associated with the underlying registration may be handled according to:

• applicable registration-data policies.
• registrar procedures.
• dispute-resolution rules.
• Privacy Policy; and
• applicable law.

Hostwover will not disclose non-public domain-registration information merely because a person claims to have a dispute with the registrant.

Disclosure may require an appropriate basis under:

• applicable policy.
• law.
• valid legal process.
• registrar procedure; or
• Hostwover's Privacy Policy.

Where the Sponsoring Registrar provides a mechanism for requesting non-public registration data, Hostwover may direct an eligible requester to that procedure.

Hostwover may preserve relevant account or domain records where reasonably necessary for:

• an active dispute.
• fraud investigation.
• legal process.
• security investigation.
• provider request; or
• protection of legal rights.

Preservation does not mean that the information will automatically be disclosed.

Hostwover may provide the Sponsoring Registrar with relevant information reasonably necessary to:

• investigate a domain dispute.
• verify registration information.
• comply with UDRP or URS.
• investigate a transfer.
• implement a decision.
• comply with a legal order; or
• maintain domain security.

Where reasonably necessary, Hostwover or the Sponsoring Registrar may communicate relevant information to the applicable registry.

Hostwover may cooperate with recognized dispute-resolution providers where reasonably necessary and permitted.

Where Hostwover is not the registrar, certain requests may need to be handled directly by the Sponsoring Registrar.

A general domain-dispute notice submitted to Hostwover should include, where applicable:

• disputed domain.
• complainant's name.
• contact information.
• nature of the claim.
• relationship to the domain.
• relevant trademark information.
• relevant court or dispute case number.
• supporting documents.
• requested action; and
• identity of any authorized representative.

Useful supporting evidence may include:

• trademark registration information.
• corporate records.
• contracts.
• invoices.
• historical registration records.
• account communications.
• transfer records.
• court documents.
• arbitration decisions.
• UDRP or URS case documents; and
• authorization records.

A person submitting a dispute notice must provide information in good faith.

Knowingly providing materially false documents or representations may result in:

• rejection of the request.
• account restrictions.
• referral to an appropriate authority; or
• other action permitted by law.

Hostwover may request verification of documents where their authenticity is uncertain.

This may include verification of:

• court orders.
• identity documents.
• company documents.
• powers of attorney.
• settlement agreements; or
• other evidence.

A lawyer, agent, employee, or other representative submitting a request may be required to demonstrate authority to act for the relevant party.

Hostwover may request additional information before:

• restricting a domain.
• changing account control.
• forwarding sensitive information.
• implementing a settlement.
• escalating a registrar request; or
• taking another significant action.

Hostwover may be unable to take action on complaints that do not provide enough information to identify:

• the domain.
• nature of the dispute.
• complaining party.
• relevant legal basis; or
• requested action.

Hostwover may acknowledge receipt of a complaint.

Acknowledgment does not mean:

• the complaint is valid.
• Hostwover agrees with the complainant.
• a violation occurred.
• the domain will be suspended; or
• ownership will change.

Hostwover may notify the affected Customer of a dispute where appropriate.

The notice may include:

• nature of the complaint.
• affected domain.
• requested information.
• applicable deadline.
• required action; and
• relevant supporting information.

Hostwover may redact or withhold information where reasonably necessary to protect:

• personal information.
• security information.
• privileged information.
• confidential provider information.
• unrelated Customer information; or
• information restricted by law.

Where Hostwover requests a response relating to a domain dispute, the Customer should respond within the specified period.

The applicable external dispute procedure may impose separate and binding deadlines.

A deadline imposed by a:

• UDRP provider.
• URS provider.
• registrar.
• registry.
• court; or
• other competent authority

may control over Hostwover's ordinary support timelines.

Hostwover cannot guarantee that it can extend a filing or response deadline imposed by another organization.

Customers must communicate directly with the relevant dispute provider where required.

Hostwover is not responsible for fees incurred by a party in connection with:

• UDRP.
• URS.
• lawyers.
• court proceedings.
• arbitration.
• expert evidence.
• registry disputes; or
• another external procedure.

Where permitted under applicable agreements, Hostwover may charge reasonable administrative fees for extraordinary work required to implement certain legal or dispute-related requests.

Any applicable fee should be disclosed where appropriate before chargeable work is performed.

The existence of a domain dispute does not automatically entitle the Customer to a refund of:

• registration fees.
• renewal fees.
• transfer fees.
• redemption fees.
• privacy fees.
• protection fees; or
• associated Service charges.

Refund eligibility is governed by the applicable Hostwover Refund Policy and product agreement.

If a domain is transferred, cancelled, suspended, or otherwise affected as a result of a valid:

• UDRP decision.
• URS determination.
• court order.
• registry proceeding.
• registrar procedure; or
• other binding dispute mechanism,

Hostwover is not required to compensate the Customer merely because the Customer loses use or control of the domain.

This does not limit rights that cannot legally be excluded.

To the extent permitted by applicable law and the Hostwover Terms of Service, Customers remain responsible for third-party claims arising from their registration or use of domain names.

Hostwover's technical cooperation with:

• a complainant.
• registrant.
• dispute provider.
• registrar.
• registry; or
• court

does not mean Hostwover endorses that party's legal position.

Hostwover may take or facilitate actions necessary to implement a binding domain-dispute decision where required by:

• applicable policy.
• Sponsoring Registrar.
• registry.
• court order.
• legal requirement; or
• contractual obligation.

Implementation may be delayed where:

• applicable policy provides a waiting period.
• qualifying court proceedings have commenced.
• the decision is stayed.
• clarification is required.
• conflicting legal process exists; or
• the Sponsoring Registrar requires additional information.

If parties settle a domain dispute while an administrative proceeding is pending, they should follow the settlement process established by the applicable dispute provider.

Hostwover may assist with domain-management actions after receiving appropriate confirmation.

Withdrawal of a complaint does not automatically remove every:

• lock.
• restriction.
• provider hold; or
• legal requirement.

Hostwover may wait for confirmation from the Sponsoring Registrar or dispute provider before restoring normal domain-management functionality.

Once a dispute concludes, applicable restrictions may be removed where:

• the dispute provider confirms completion.
• the Sponsoring Registrar permits removal.
• no court action prevents removal.
• no other dispute remains pending; and
• no separate security restriction applies.

Where an ownership dispute involved suspected compromise, Hostwover may require additional security measures before restoring full account control.

Measures may include:

• password reset.
• multi-factor authentication.
• email verification.
• account review.
• session revocation; or
• additional ownership verification.

A domain dispute does not automatically determine ownership of related Hostwover Services such as:

• hosting.
• VPS.
• VDS.
• professional email.
• Google Workspace.
• SSL.
• backups; or
• account balances.

These services may require separate authorization or legal determination.

Transfer of a domain to another person or registrar does not automatically transfer associated:

• website files.
• databases.
• email.
• server resources.
• subscriptions; or
• other Customer data.

Hostwover will not automatically disclose website, mailbox, server, or account data to a party merely because that party obtains rights to the domain name.

Separate privacy, account-ownership, contractual, and legal considerations apply.

A domain transfer or ownership change may affect:

• DNS.
• nameservers.
• websites.
• email.
• APIs; and
• other connected services.

The receiving party is responsible for ensuring appropriate configuration after the transfer.

Hostwover may restrict accounts or reject requests where there is credible evidence that a person is abusing the dispute process through:

• forged documents.
• impersonation.
• fraudulent court documents.
• fabricated trademark claims.
• false ownership evidence; or
• social engineering.

Customers must not attempt to evade a dispute lock through:

• unauthorized account transfers.
• false registration information.
• new registrar accounts.
• fraudulent registrant changes.
• provider manipulation; or
• other deceptive means.

A fraudulent attempt to manipulate ownership of a domain may result in account or Service restrictions under applicable Hostwover policies.

Hostwover support does not provide legal advice concerning:

• trademark rights.
• domain ownership.
• UDRP strategy.
• litigation strategy.
• jurisdiction.
• copyright.
• contractual rights; or
• other legal disputes.

Parties should consult qualified legal counsel where appropriate.

Hostwover does not guarantee the outcome of:

• UDRP proceedings.
• URS proceedings.
• registrar disputes.
• registry disputes.
• court proceedings.
• arbitration.
• settlement negotiations; or
• domain-recovery attempts.

Where a domain has already been transferred, deleted, expired, or otherwise moved outside Hostwover's effective control, recovery may not always be possible.

Hostwover may provide reasonable assistance where available.

Hostwover is not responsible for independent decisions made by:

• ICANN.
• a registrar.
• registry.
• dispute-resolution provider.
• panelist.
• court.
• arbitrator; or
• government authority.

Domain registrations supplied through Hostwover remain subject to applicable requirements of the Sponsoring Registrar and registry.

Current upstream registration agreements may themselves incorporate applicable UDRP, URS, transfer-dispute, and registry-specific procedures.

If this Policy conflicts with a mandatory:

• ICANN policy.
• UDRP provision.
• URS procedure.
• registry rule.
• registrar rule.
• court order; or
• applicable law,

the mandatory external requirement will control to the extent of that conflict.

The Hostwover Domain Registration Agreement establishes the Customer's general contractual responsibilities relating to registration and use of domains.

This Domain Dispute Policy explains the procedures applicable when rights or control over a domain are disputed.

Transfer requests involving disputed domains remain subject to the Hostwover Domain Transfer Agreement and applicable registrar-transfer rules.

A valid transfer request may still be denied where a mandatory dispute-related restriction applies.

The Abuse Handling Policy applies primarily to abuse involving domains or Services, such as:

• phishing.
• malware.
• botnets.
• fraud.
• DNS abuse; or
• security threats.

This Domain Dispute Policy primarily addresses competing legal, registration, trademark, transfer, and ownership claims relating to domain names.

Activity involving a disputed domain may separately violate the Hostwover Acceptable Use Policy.

Hostwover may address that abuse independently of the ownership dispute.

Hostwover may update this Policy to reflect:

• changes to ICANN policies.
• changes to UDRP or URS.
• registrar requirements.
• registry requirements.
• new domain extensions.
• legal requirements.
• provider changes; or
• operational improvements.

External domain policies may change independently of Hostwover.

The then-applicable mandatory policy will govern where required even if this Hostwover Policy has not yet been updated to reflect a recent external change.

Where required by applicable law, Hostwover may provide reasonable notice of material changes to this Policy.

Changes to this Policy are not intended to alter the governing procedural rules of a dispute already properly commenced under a separate mandatory dispute-resolution procedure.

The applicable dispute provider or governing policy determines which version applies to that proceeding.

If any provision of this Policy is found invalid or unenforceable, the remaining provisions will continue to apply to the maximum extent permitted by applicable law.

Hostwover's failure to exercise a right or restriction in one dispute does not waive its ability to exercise that right in another appropriate circumstance.

Hostwover may provide translations of this Policy.

Where legally permitted and unless expressly stated otherwise, the English version will control in the event of a material inconsistency between translations.

For purposes of this Policy:

"Complainant" means a person or entity asserting rights against a domain registration.

"Customer" means a person or entity purchasing, controlling, administering, or using a domain-related Hostwover Service.

"Disputed Domain" means a domain subject to a material ownership, trademark, transfer, administrative, arbitral, or legal dispute.

"Registrant" means the registered domain-name holder according to the applicable registration framework.

"Registry" means the organization responsible for operating the applicable top-level domain registry.

"Sponsoring Registrar" means the registrar responsible for sponsorship of the domain registration at the registry.

"UDRP" means the Uniform Domain Name Dispute Resolution Policy where applicable.

"URS" means the Uniform Rapid Suspension System where applicable.

"Dispute Provider" means an organization authorized to administer an applicable domain-name dispute-resolution proceeding.

"Domain Lock" means a restriction preventing some or all changes to a domain while an applicable condition or proceeding exists.

"Change of Registrant" means a change to registrant information that constitutes a Change of Registrant under the applicable registrar or ICANN framework.

Hostwover's approach to domain disputes is guided by the following principles:

1. Hostwover will not pretend to be the legal adjudicator of private domain disputes.
2. domain disputes should use the appropriate recognized dispute or legal procedure.
3. trademark ownership alone does not automatically authorize a domain transfer.
4. account access alone does not conclusively establish legal ownership.
5. payment alone does not conclusively establish legal ownership.
6. Hostwover may verify identity and authority before sensitive changes.
7. Hostwover may preserve the status quo during a recognized dispute.
8. mandatory domain locks and transfer restrictions will be respected.
9. Hostwover may escalate matters to the Sponsoring Registrar or registry.
10. UDRP and URS decisions are made by the applicable external dispute process, not Hostwover.
11. abuse and ownership disputes may be investigated separately.
12. court orders will be reviewed and handled through the appropriate registrar or legal process.
13. Customer data will not be disclosed merely because another party claims ownership of the domain.
14. binding decisions may result in transfer, suspension, cancellation, or another required domain action.
15. Customers remain responsible for monitoring dispute deadlines and renewal requirements; and
16. Hostwover will make commercially reasonable efforts to implement valid domain-dispute requirements within its actual technical and contractual authority.

Domain-related disputes may currently be submitted to:

Hostwover Support

Email: [email protected]

Website: hostwover.com

When contacting Hostwover regarding a domain dispute, include:

• the disputed domain.
• your full name or organization.
• your relationship to the domain.
• relevant case number, if any.
• relevant supporting documentation; and
• a clear description of the requested action.

Do not send passwords, Auth/EPP codes, private keys, full payment-card numbers, or unnecessary authentication credentials by email.

Where a dispute is already pending before a:

• UDRP Provider.
• URS Provider.
• court.
• arbitrator.
• registry.
• registrar; or
• another recognized dispute authority,

communications and documents required by that proceeding should be submitted through the procedure specified by that authority.

Sending documents only to Hostwover does not replace a required filing with the appropriate dispute authority.

This Domain Dispute Policy becomes effective on the date shown above and applies to domain-related Services that reference or incorporate this Policy.

END OF DOMAIN DISPUTE POLICY