.tr Domain Disputes: A Guide to TRABİS and Dispute Providers
Understand .tr domain disputes, TRABİS, provider selection and evidence checks without importing UDRP rules automatically.
What’s in this article?
Direct answer
A .tr complaint cannot be prepared by replacing the extension in a UDRP template. The Turkish dispute mechanism, current legislation and the authorised provider's procedure must be examined together. TRABİS operates the registration system; that role should not be confused with deciding every dispute.
An important distinction
TRABİS describes similarity or identity with a relevant trademark, trade name, business name or other identifying sign; absence of a legal right or connection; and bad-faith allocation or use. The word “or” must not be silently replaced with the UDRP formulation concerning registration and use. This difference identifies questions to investigate, not a guaranteed outcome.
Document the right relied upon and its connection with the complainant. A trade name does not create unlimited entitlement to every similar address. Investigate possible rights or connections of the holder before making categorical allegations.
Choosing a provider
Verify the current authorised UÇHS list through TRABİS. Record the provider, application channel, procedural text, tariff and date checked. A prominent advertisement is not evidence of authorisation. A provider's commercial arbitration service may operate under different rules from its domain dispute service.
Registration and acquisition dates, the former registration regime and transitional provisions require separate attention. Do not assume that all historical .tr registrations fall under identical conditions. Obtain current procedural clarification where applicability remains uncertain.
Fictional example
A former dealer continues using an address that appears to offer official servicing. Put the contract, termination notice and current page on a single timeline. The end of authorisation is relevant, but does not answer every question about the disputed registration and use.
Filing checklist
- Is the extension actually .tr?
- Are the complainant and asserted right correctly identified?
- Is the provider currently authorised?
- Have applicable dates and transitional rules been examined?
- Are related court proceedings coordinated?
- Does each requested outcome have supporting evidence?
Document procedural verification
Record the instrument's name, access link and date checked at filing. If the provider's form requires information not covered by a general guide, do not fill the gap by guessing. Identify which document supports each allegation. A provision that could not be accessed should not be marked as verified.
An earlier allocation record or relationship document submitted by the holder may change the analysis. Separate confirmed records from open questions in the initial summary rather than declaring the result in advance. Track costs and later technical implementation as well: submitting the form is not itself closure.
Questions
Does contacting TRABİS transfer the domain? Contact with the registration system is not itself a dispute decision.
Does this alternative route eliminate courts? No general exclusion should be assumed; the applicable judicial steps and timing require separate assessment.
Official sources
Related guides
- Resolving Domain Name Disputes: A Decision Guide for Brand Teams
- UDRP or URS? Transfer, Suspension and Evidence Compared
- Responding to a Domain Complaint: Preparing the Defence File
- After a UDRP Decision: From Legal Outcome to Domain Control
Brand protection and monitoring
General information only. Rights, authority and current procedure require case-specific assessment. Fictional examples are not B10 client cases or claimed successes.