Domain ownership disputes and UDRP

A 15-minute guide. Think of a domain as a house, and every case gets easier to sort.

  • Sort any case into claim, dispute or UDRP
  • Follow the UDRP steps
  • Know what never to do
During a UDRP, never unlock, move or transfer the domain. If you remember one thing from this guide, make it this.

Sort a case in three questions

Think of a real or made-up customer case and answer honestly.

Three terms

First, meet the cast. Then the three kinds of case.

🏠The domainis the house.
📜The registrantis the name on the deed.
🔑Hostingeris the key office. We hold the keys and follow the rules. We are not a judge.
⚖️The provider(WIPO, ADR or ADRFORUM) is the judge in a UDRP.

Ownership claim

The requester is the registrant, or their details match the registrant data.

We verify ID and selfie. Compliance is involved once all documents are in.

Ticket: Domain – Move

Dispute

Two parties both claim the domain, or the registrant's details don't match the requester, or a third party (developer, agency) won't transfer it.

We can't help. The customer resolves it privately or through the authorities. Hostinger does not arbitrate.

Ticket: none for Compliance

UDRP

ICANN's Uniform Domain-Name Dispute-Resolution Policy, for trademark or bad-faith complaints. An approved provider (WIPO, ADR or ADRFORUM) runs it.

Hostinger implements the ruling. It doesn't decide it.

Action: keep the lock, follow the steps below

What to do when there is a UDRP

Follow these in order.

  1. Check the CRM note for a Compliance note on the domain.
  2. Tell the customer that all UDRP updates go to the registrant's email from WIPO, and to check spam and trash too.
  3. Do not unlock, move or transfer the domain while the UDRP is open.
  4. Ask Compliance only if the CRM note doesn't name the authority (WIPO, ADR, ADRFORUM).
Why the system backs this up From 16–17 Nov, a UDRP lock cancels pending outgoing moves and IRTP transfers, blocks contact changes, and voids superseded moves. Policy and system now agree (DMNS-6665, DMNS-6803).
If the lock tool fails A 9 Nov thread reports the CRM UDRP lock tool failing on one case. If you hit it, check with the Compliance team before doing anything manual.

Practice cases

Decide your answer first, then open the case to check.

Case A. The developer registered the customer's domain under the developer's own name and refuses to transfer it.
Dispute. No Compliance ticket.

Tell the customer that Hostinger can't intervene and the parties must resolve it privately or via the authorities.

Keep our internal approval path out of it Explaining it invites "then just change the email for me".
Case B. The customer provides ID and a selfie matching the registrant data, and there is no third-party conflict.
Ownership claim

Involve Compliance after all documents are in, via a Domain – Move ticket.

Case C. CRM shows a WIPO UDRP note and the customer asks to unlock the domain to move it to another account.
UDRP. Refuse.

Do not unlock or move. Send the UDRP predefined reply, which points to WIPO and the registrant email.

Special case: legal or ICANN escalation

A gTLD first registered before 21 Aug 2025, where the customer asks for personal registrant details and raises a legal or ICANN escalation.

  1. Ask for photo ID and a selfie.
  2. Open a Domain ticket for T2 to post in #legal-compliance-cases.
  3. Never send legal@hostinger.com.

Self-check

Answer in your head, then open to compare.

1. Who decides a UDRP outcome?

The provider. Hostinger implements the ruling.

2. Can you unlock a domain while a UDRP is open?

No.

3. Where do UDRP updates reach the customer?

The registrant's email, sent by WIPO.

4. A dispute between a customer and their developer: which ticket goes to Compliance?

None. The customer resolves it.

Cheat sheet

Same house, three different situations.

Ownership claim

Your name is on the deed. You show ID at the key office and they check it matches.

Looks like
Requester is the registrant, or matches the registrant data.
Who decides
Compliance, once all documents are in.
You do
Verify ID and selfie. Open a Domain – Move ticket.

Dispute

Two people say the same house is theirs. The key office can't pick a winner.

Looks like
Two claimants, details don't match, or a developer or agency won't transfer.
Who decides
Not us. The parties settle it privately or through the authorities.
You do
Explain that we can't intervene. No Compliance ticket.
Never
Explain our internal approval path.

UDRP

A judge has sealed the house. The key office can't hand over keys or move it until the ruling.

Looks like
Trademark or bad-faith complaint. CRM note names WIPO, ADR or ADRFORUM.
Who decides
The provider. We carry out the ruling.
You do
Check the CRM note. Point the customer to the registrant email. Send the UDRP predefined reply.
Never
Unlock, move or transfer the domain.

The three judges

WIPO, ADR and ADRFORUM are the three "judges" that ICANN has approved to handle domain disputes. A UDRP complaint goes to one of them, not to ICANN directly and not to Hostinger.

🌍

WIPO

World Intellectual Property Organization
  • The biggest and best known of the three.
  • A United Nations agency based in Geneva, Switzerland.
  • Handles the majority of UDRP cases globally.
  • Very commonly used by big brands to reclaim domains.
  • A panel of expert arbitrators reviews the case and makes the decision.
⚖️

ADR

Alternative Dispute Resolution (Czech Arbitration Court)
  • Based in Prague, Czech Republic.
  • Handles UDRP disputes, and specialises in .EU domain disputes.
  • Smaller than WIPO but fully ICANN-accredited.
  • Often used for European trademark cases.
🏛️

ADRFORUM

National Arbitration Forum
  • Based in the United States.
  • One of the original ICANN-approved dispute resolution providers.
  • Handles UDRP cases, and is especially popular with US-based companies.
  • Also handles disputes for certain new gTLDs (like .store and .tech).
Quick summary All three do the same job: they review UDRP complaints and decide who gets the domain. The complainant (for example, a brand) chooses which body to file with.

As CS, you don't need the details of each case. Just do this:

  1. Check the CRM for which body is handling it.
  2. Tell the customer to check their registrant email.
  3. Never unlock or transfer the domain while a case is active.
  4. Escalate to Compliance if the body isn't mentioned in the CRM.