Setting the expectation is part of the work. A stakeholder told a domain will be gone today, who then watches it serve a login page for four more days, stops believing the next estimate.
Realistic timelines
| Route | Best case | Typical | Never |
|---|---|---|---|
| Major hosting provider with a real abuse process | An hour | Same day | — |
| Small or offshore host | A day | Days, if at all | Common |
| CDN or proxy | Hours | Days, or a refusal on conduit grounds | Common |
| Registrar, well-evidenced report | Same day | Two to five days | Some registrars, routinely |
| Certificate revocation | A day | Days, and it changes little | — |
| Registry escalation | Days | Weeks | Frequently |
| UDRP | Weeks | Two to four months | — |
What UDRP is for
The Uniform Domain-Name Dispute-Resolution Policy transfers a domain to a trademark holder who proves three things: the domain is confusingly similar to their mark, the holder has no legitimate interest in it, and it was registered and is being used in bad faith.
- It takes months and costs a filing fee plus legal time.
- It transfers the domain to you rather than merely suspending it, which is its distinctive value.
- It requires a registered trademark. No mark, no filing.
- It is useless for an active campaign. The domain will have finished its work and been abandoned long before a panel reports.
When UDRP is the right tool
For a domain that is valuable to you and is being held rather than actively abused — a squatter sitting on your brand name, a former partner who will not release a name, a domain being offered back to you at a price. It is a property dispute mechanism, and it works well as one.
Never present UDRP as an incident response
It is the answer to “how do we get this domain permanently” and never the answer to “how do we stop this campaign”. Offering it in an incident conversation reads as not understanding the timescale, and it is the response a panicked stakeholder most often asks for by name.