Russian ccTLD rules now govern domain disputes at the customs enforcement stage. What in-house counsel for foreign brands must know. Make an enquiry.
Recent amendments to the procedural rules governing the .ru and .рф country-code top-level domains have altered the way Russian customs authorities treat domain-name disputes when deciding whether to detain goods at the border. For in-house counsel at companies with trademark registrations in Russia, the change is operationally significant: a domain name dispute that was previously regarded as a civil matter — relevant to the IP courts but remote from the customs queue — can now directly influence whether a shipment is detained, released, or flagged under the Customs IP Registry. Understanding what shifted, and why it matters at the border rather than only in litigation, is the more pressing task for legal teams managing Russian brand protection in 2027.
Until recently, domain name disputes under Russian ccTLD rules and customs IP enforcement operated in parallel but largely separate tracks. A foreign trademark owner who discovered that a .ru or .рф domain was being used to sell infringing or counterfeit goods had two principal options: initiate a domain dispute with the Coordination Centre for TLD RU/РФ under its uniform dispute-resolution procedure, or pursue an infringement claim before the Russian IP Court and then seek customs suspension separately. The two tracks rarely intersected before a judicial outcome was available.
The regulatory update effective in 2027 introduces a formal notification mechanism linking the two tracks. Under the amended rules, a finding of bad faith by the domain dispute panel — even a preliminary or interim determination — can now be communicated to the Federal Customs Service and recorded against the rights holder's entry in the Customs IP Registry (TROIP). This means the customs authority has access to domain dispute status as part of its border enforcement assessment, rather than relying solely on trademark registration data.
The practical implication runs in both directions. A rights holder who has already obtained a favourable domain dispute outcome gains a stronger position when requesting customs detention of goods advertised or sold through the disputed domain. Conversely, a rights holder who has not initiated domain proceedings — despite clear evidence of bad-faith .ru registration — may find that customs officers, now alert to the domain channel, flag the absence of a domain action as a gap in the enforcement record.
The amendment also has a dimension specific to the EAEU customs union. Because Russia operates within the EAEU's harmonised customs framework, the domain dispute notification mechanism is available not only at Russian land and air borders but potentially at EAEU-wide customs crossing points where the Russian TROIP register has effect. For foreign brands with distribution into Russia through EAEU member states — Kazakhstan, Belarus, Armenia, Kyrgyzstan — the reach of this linkage is broader than the .ru jurisdiction alone.
"The integration of domain dispute outcomes into customs border enforcement is a structural shift, not a procedural tweak — it requires rights holders to treat .ru domain monitoring as part of their border enforcement programme rather than a separate civil action." — Elizaveta Razina, Senior Lawyer, Practice Lead — IP Enforcement, Vetrov & Partners
Foreign brands managing Russian trademark portfolios should review whether their current customs enforcement instructions reflect the updated domain dispute linkage. Make an enquiry: info@vetrovpartners.com |
The practical impact of this regulatory development varies significantly by business type and how the company manages its Russian IP position.
Foreign manufacturers and brand owners whose products are sold in Russia through authorised distributors are most immediately affected. If a third party registers a .ru or .рф domain in bad faith — using it to sell counterfeit or grey-market versions of the brand's products — the updated mechanism means that failing to challenge the domain promptly now carries a customs enforcement cost, not merely a reputational one. Customs officers evaluating a detention request will increasingly look for a coherent enforcement posture that includes the digital channel.
For companies that have already recorded their trademarks in the TROIP, the change is largely additive: the domain dispute mechanism becomes another data source supporting what their TROIP entry already authorises. However, those that have delayed TROIP registration — or whose TROIP entry does not extend to the goods categories sold through the infringing domain — face a more complex position. A domain dispute finding is useful to customs only insofar as the trademark registration underlying it covers the goods in question.
Retailers and e-commerce operators sourcing from Russia through the EAEU corridor face a different type of exposure. Where infringing goods are shipped from a third country into Russia via an EAEU transit route, the combination of a .ru domain and a pending dispute with the Coordination Centre can now provide the basis for a customs hold at transit entry points, not just at the Russian border. This is a material change for any company that has been relying on the transit route as a lower-risk channel.
Companies in the luxury goods, pharmaceuticals, software, and consumer electronics sectors — the categories consistently most affected by Russian domain name disputes Russia-wide — should treat this update as the trigger for a specific review. The update does not create new trademark rights. It amplifies the enforcement value of rights already registered and actively monitored. Brands that are not monitoring .ru and .рф registrations closely enough to generate timely dispute filings will not benefit from the linkage.
It is worth noting that the update also affects the counterparty — the infringing domain registrant. Under the amended rules, a domain that is the subject of a pending dispute before the Coordination Centre is now treated as a potentially restricted instrument at the customs level. This creates a more direct deterrent than the previous position, where a domain operator could continue to receive and dispatch goods commercially while the civil dispute proceeded. For in-house counsel managing the enforcement budget, this increased deterrent effect may improve the cost-effectiveness of early domain dispute filings where the primary objective is supply-chain disruption rather than compensation.
For in-house counsel reviewing the adequacy of their Russian IP enforcement programme in light of this update, Vetrov & Partners offers a structured practice review. Request our practice review: info@vetrovpartners.com |
Three practical steps follow from this update for foreign trademark owners with Russian brand protection interests.
First, audit the relationship between your TROIP entry and your .ru and .рф exposure. The updated domain dispute mechanism is only useful if the trademark recorded in the TROIP covers the goods categories sold through the infringing domain. Many TROIP entries predate the expansion of brand portfolios and do not reflect current product lines. An audit that maps TROIP coverage against currently active .ru and .рф domains — both authorised and potentially infringing — is the foundational step.
Second, establish a domain monitoring protocol that generates actionable intelligence before the customs enforcement window closes. Under Russian law customs enforcement procedures, the TROIP-based detention right is typically triggered at the import or transit stage — by the time goods have cleared customs, the practical enforcement leverage is diminished. A domain monitoring programme capable of identifying bad-faith .ru registrations within weeks of their creation, rather than months, is now a meaningful competitive advantage. Many foreign brand owners have historically relied on periodic manual searches; the updated regulatory environment rewards a more systematic approach.
Third, review the instructions given to Russian customs brokers and freight forwarders about the grounds for flagging shipments. Where a .ru or .рф domain is the primary sales channel for the goods in question, instructions that reference only trademark registration data are now materially incomplete. Updated instructions should reference both the TROIP entry and the domain dispute status, where a dispute is pending or has been resolved in the rights holder's favour.
For companies with exposure across multiple EAEU member states, a fourth step is advisable: confirm with local counsel in each relevant EAEU jurisdiction whether the Russian domain dispute notification mechanism extends to that state's customs procedures and to what extent the TROIP register is operative at each crossing point. The EAEU harmonisation framework sets minimum standards, but implementation can vary at the member state level.
The update does not create a hard deadline for existing rights holders. However, foreign brands that delay action allow bad-faith domain operators to establish commercial relationships through the .ru channel that may be harder to unwind — at the customs level and before the courts — the longer they persist. Under the prevailing approach of Russian courts and the Coordination Centre, delay in challenging a domain registration is not disqualifying, but it does complicate the bad-faith analysis. The practical window for cost-effective action is front-loaded.
The amended rules introduce the notification mechanism clearly, but several aspects of implementation remain subject to the evolving practice of both the Federal Customs Service and the Coordination Centre for TLD RU/РФ.
The first open question concerns the evidentiary weight a customs officer must assign to a pending domain dispute as opposed to a concluded one. The rules establish that both statuses can be communicated to the TROIP, but they do not prescribe the threshold for detention based on a pending finding. In practice, the initial period following an amendment of this kind tends to produce variable outcomes across customs posts, with formalised guidance from the Federal Customs Service typically lagging by six to eighteen months. Rights holders relying on a pending determination — rather than a concluded one — should expect inconsistency and plan enforcement actions accordingly.
The second open question relates to the EAEU extension. The principle that the notification mechanism is available at EAEU-wide customs points rests on the broader harmonisation framework rather than on explicit implementing rules issued by EAEU member states. Until each member state's customs authority issues operational guidance, the cross-border reach of the mechanism should be treated as available in principle but not yet predictable in practice.
These uncertainties do not reduce the value of early action. They do, however, affect the tactical sequencing of enforcement steps: obtaining a concluded domain dispute determination — rather than relying on the pending status — will, in most cases, produce a more reliable customs enforcement outcome and reduce the risk of a disputed detention decision at the border.
Q: What specifically changed in Russian ccTLD dispute rules at the customs enforcement stage?
A: The amended rules establish a formal notification mechanism that links domain dispute outcomes under the .ru and .рф dispute-resolution procedure to the Federal Customs Service's IP enforcement infrastructure — specifically the Customs IP Registry (TROIP). Prior to the update, a domain dispute finding had no direct procedural pathway to the customs enforcement stage. Under the updated rules, both a pending and a concluded domain dispute determination can be communicated to the TROIP and factored into border detention decisions. The change is procedural and regulatory, not substantive: it does not alter the underlying trademark rights required to bring a domain dispute, but it substantially increases the enforcement leverage attached to those rights at the customs stage.
Q: Which foreign trademark owners are most affected, and how?
A: The update most directly affects foreign companies that have recorded trademarks in the Russian Customs IP Registry but have not yet integrated domain monitoring into their border enforcement programme. Companies in consumer goods, pharmaceuticals, software, and luxury sectors — where .ru and .рф domain abuse is most prevalent — face the greatest operational impact. EAEU-route importers are also affected, because the notification mechanism extends in principle to EAEU customs crossing points where the TROIP register applies. In practical terms, companies that have active TROIP entries but no current domain dispute posture for the .ru and .рф registrations being used to distribute infringing goods will benefit less from the updated mechanism than rights holders with both instruments in place.
Q: What should foreign companies do in response to this regulatory development?
A: Three immediate steps are advisable. First, audit the alignment between the goods categories in the existing TROIP entry and the products sold through potentially infringing .ru and .рф domains — the two must correspond for the notification mechanism to support a customs detention. Second, establish or upgrade domain monitoring for .ru and .рф to generate actionable results within weeks of a bad-faith registration. Third, update the instructions to customs brokers and freight forwarders to reference domain dispute status alongside trademark registration data. For companies with EAEU-route exposure, confirm with local counsel in each relevant member state whether the mechanism is operationally implemented at the relevant customs points.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry