Step-by-step: recover a .jp domain from a serial cybersquatter

Step-by-step: recover a .jp domain from a serial cybersquatter. UDRP and ccTLD domain recovery and defense across .jp. Email the firm to assess your case.

A brand owner finds its Japanese trademark registered as a .jp domain by a registrant who holds dozens of similar names across multiple zones. The registrant is not using the domain – it simply sits there, resolving to a parking page or nothing at all. A five-figure buy-back demand arrives shortly after the brand owner makes contact. That pattern is textbook serial cybersquatting, and it is precisely the fact pattern that the Japan Domain Name Dispute Resolution Policy – the JP-DRP – was designed to address.

To recover a .jp domain from a serial cybersquatter you must satisfy all three elements of the JP-DRP's core test: confusing similarity to a mark you hold, no legitimate interest on the registrant's side, and bad-faith registration and use. A response is due within 20 days of commencement, and a standard case is normally concluded within approximately two months. The only remedies are transfer or cancellation – no monetary damages are available.

This guide walks each step in sequence, flags the procedural trap concealed within it, and shows how a serial-cybersquatter record strengthens your case at every stage.

What governs .jp disputes – and why it matters before you file

The JP-DRP is the dedicated administrative dispute-resolution procedure for .jp domains, administered by the Japan Network Information Center (JPNIC) and its associated dispute-resolution providers. It closely tracks the structure of the UDRP – the same three-element test, the same transfer-or-cancellation remedy framework, the same prohibition on monetary awards – but it is a distinct procedure with its own rules, filing requirements, and language expectations. You cannot simply repurpose a WIPO complaint drafted for a .com and submit it for a .jp domain. The procedural differences are real and the filing must address them directly.

Why does this matter before a single line of the complaint is written? Because the choice of route shapes every subsequent step. If the registrant also holds a .com or other gTLD version of your mark, the UDRP at WIPO or the Forum addresses those zones, while the JP-DRP addresses .jp. Coordinating or sequencing multi-zone filings is a strategic question that deserves early attention: a decision in one proceeding can be cited as persuasive – though not binding – in another. In our practice, we routinely map all zones the cybersquatter holds before drafting a single complaint, precisely to avoid a sequence that leaves the most valuable domain as the last one recovered.

One further preliminary point. The JP-DRP does not require the complainant to hold a Japanese trademark. Rights in a mark recognized under applicable law – including rights established by use – can satisfy the first element. The trap here is assuming that a foreign brand owner without a registered Japanese mark has no standing. That assumption loses cases that should be won.

For a read on whether the three JP-DRP elements are met in your situation, reach us at info@cognomenlaw.com.

How do you identify a serial cybersquatter before filing?

Identifying the registrant as a serial cybersquatter is not merely satisfying – it is strategically valuable evidence. Paragraph 4(b) of the UDRP (and its JP-DRP counterpart) lists a pattern of abusive registrations as a non-exhaustive indicator of bad faith. The more clearly that pattern is documented, the harder it is for the registrant to claim coincidence or independent legitimate purpose.

Start with WHOIS/RDDS data for the disputed .jp domain. Note the registrant's name, organization, email domain, and registration date. Then search across all zones: .com, .net, .org, and other gTLDs, plus additional ccTLDs. Look for the same registrant name or organization, the same administrative contact email, or the same registrar account fingerprint. Domain search tools that aggregate ownership records across zones are useful at this stage. The goal is a documented list – with screenshots – of every domain the registrant holds that corresponds to a third-party mark.

The trap in this step: WHOIS data for many .jp domains is thin under modern privacy rules. A registrant using a privacy or proxy service may not be immediately identifiable. Do not stop there. Cross-reference the IP address the domain resolves to, the name server configuration, the parking page content or affiliate code, and any registrar-specific patterns. Panels examining serial-cybersquatter claims have consistently held that a registrant cannot hide a pattern of abusive registrations behind a series of privacy shields if the underlying technical and commercial facts tell a coherent story.

In a recent matter (a .jp domain together with four .com variants, autumn 2024), we assembled ownership records linking a single registrant to approximately a dozen third-party brand names across multiple zones. That pattern record was central to the bad-faith finding – the registrant offered no explanation and did not file a response.

Step 1 – Establish your trademark rights before anything else

The first element of the JP-DRP test – confusing similarity to a mark you hold – is usually the easiest to satisfy, but it contains a preparation trap that slows or weakens the filing if not addressed upfront. Your trademark rights must be documented and submitted with the complaint. Panels do not search trademark registers themselves.

Gather the following before filing: certified or official copies of each trademark registration relied upon (or, if relying on unregistered rights, the best available evidence of use – advertising materials, sales records, press coverage, dates of first use, market reach). Include registrations in any country that predates the domain registration: JP-DRP panels, like UDRP panels, accept rights in marks recognized under any applicable law, not only Japanese registrations. Organize the evidence chronologically. The panel needs to see that your rights predate the domain's registration date. If they do not – if your trademark was registered or first used after the .jp was created – you face a materially harder case and must address the timeline argument directly.

The trap here is the registration date of the .jp domain, not the registration date you find on WHOIS today. Domains can be renewed repeatedly; the relevant date is the original registration, which you may need to retrieve through historical WHOIS records or a registrar query. If the registrant registered the .jp shortly after your brand launch or your trademark application became publicly searchable, that timing itself is evidence of targeting. Document it precisely.

Step 2 – Prove the registrant has no legitimate interest

The second element – no rights or legitimate interests – places the initial burden on the complainant to make a prima facie case, after which the burden shifts to the registrant to produce evidence of legitimacy. Serial cybersquatters rarely produce any. But "rarely" is not "never," and a complainant who fails to anticipate a plausible defense leaves the panel with an unanswered question.

The Paragraph 4(c) safe harbors – a bona fide offering of goods or services before notice of the dispute, being commonly known by the name, or legitimate noncommercial or fair use – are the registrant's standard lines of defense. For a serial cybersquatter, none of these typically applies: the registrant is not known by your brand name, is not offering goods or services under it, and is not engaged in commentary or criticism. The parking page or the empty resolution is the tell. Document the current and historical use of the domain: screenshots, Wayback Machine captures, any redirects or monetization. A domain that has never resolved to anything other than a parking page carrying no plausible association with the registrant's own business is a domain with no evident legitimate interest.

The trap: do not assume the lack of a website is self-evidently sufficient. Panels have held that passive holding alone can satisfy the bad-faith element (discussed below), but the legitimate-interest analysis is separate. Affirmatively show, through the documented pattern and the domain's history, that the registrant registered the name because of your mark – not for any independent commercial reason.

Step 3 – Build the bad-faith case around the pattern record

Bad faith is where a serial-cybersquatter case either consolidates or falls apart. The JP-DRP, following the UDRP structure, requires that the domain was registered and is being used in bad faith. Both limbs matter. The serial-cybersquatter pattern addresses both simultaneously: a registrant who has made a business of registering third-party brand names has plainly registered in bad faith, and the use – whether active misdirection, a parking page monetizing brand traffic, or a naked hold pending a ransom demand – satisfies the use limb.

The non-exhaustive bad-faith indicators in Paragraph 4(b) include: registration primarily to sell the domain to the mark owner at a price exceeding out-of-pocket costs; registration primarily to disrupt a competitor's business; intentional attempts to attract users for commercial gain by creating confusion with the complainant's mark; and a pattern of abusive registrations. For a serial cybersquatter, the last factor is often the one that turns a case from arguable to clear. Document every domain in the pattern with a brief note on the third-party brand it targets. The panel does not need to investigate each one; the complainant presents the record.

What about passive holding – a domain that resolves to nothing at all? Panels under both the UDRP and analogous ccTLD rules have consistently held that passive holding does not insulate a registrant from a bad-faith finding where the surrounding circumstances – including the serial pattern, the absence of any plausible legitimate use, and the strength of the complainant's mark – make it implausible that the registrant could use the domain in good faith. That reasoning applies with particular force to a serial cybersquatter. Reference the passive-holding analysis in your complaint; do not leave the panel to infer it.

See also our detailed treatment of this doctrine: recovering a domain from a passive-holding registrant.

Step 4 – Draft, format, and file the JP-DRP complaint correctly

A substantively strong case can be procedurally derailed by a complaint that fails the JP-DRP's formatting requirements. The procedure has specific rules on language (Japanese is the default administrative language for .jp proceedings unless both parties agree otherwise or the panel orders a change), word or page limits, required annexes, and the method of service. Do not assume a template drafted for WIPO will satisfy JP-DRP requirements without modification.

The complaint must identify the disputed domain or domains, identify the complainant and the registrant (to the extent known), set out the three-element argument with supporting evidence as annexes, and specify the remedy sought (transfer or cancellation). Where the registrant's identity is masked by a privacy service, the complaint should name the privacy service as the registrant of record while noting the underlying registrant as unknown – the provider will instruct the registrar to reveal or substitute registrant details on commencement.

The trap in the filing step is the multi-domain question. A single complaint may cover multiple domains only where the same registrant holds all of them. For a serial cybersquatter, this is often true – and filing a single consolidated complaint is more cost-efficient than multiple separate proceedings. But if any domain is registered to a different entity, even a related one, it cannot be consolidated without procedural risk. Verify each domain's registrant record independently and at the time of filing, not at the time of initial investigation, because ownership can change.

WIPO and the Forum are established providers for UDRP proceedings concerning gTLDs. For .jp specifically, the applicable provider is designated under JPNIC's rules. Verify the current designated provider directly with JPNIC before filing, as provider designations for ccTLD procedures can change and are not authoritatively tracked in secondary sources. Our practice maintains current procedural contacts for the principal ccTLD procedures globally.

Step 5 – Manage the response window and the decision phase

Once the complaint is filed and commencement is notified, the registrant has 20 days to file a response. That window is fixed. Extensions are narrow and procedurally controlled. In our experience, serial cybersquatters frequently default – they do not respond, because they have no legitimate case to make and because a documented pattern record leaves no credible defense.

Default does not mean automatic transfer. The panel still examines the complaint on its merits and must be satisfied that all three elements are proven. A weak complaint that relies on the registrant's silence to plug evidentiary gaps can still fail. The complainant's obligation is to build a case that stands on its own. Default removes the opposition; it does not lower the standard.

If the registrant does respond, expect one of three lines of argument: a claim of prior rights or independent legitimate use of the name; a challenge to the complainant's trademark rights (typically a date or scope argument); or a good-faith registration argument distinguishing the pattern record (claiming the domains were registered without knowledge of the complainant's mark). Each of these is answerable with the evidence assembled in steps 1–3 above, which is why front-loading the evidence preparation matters.

Panel appointment follows the close of the response window. A standard single-member panel case is normally decided within approximately two months of commencement. The decision is published and, if transfer is ordered, the registrar implements the order after a brief implementation period unless court proceedings are notified.

If a prior filing produced an adverse outcome or if you have already received a demand letter, email info@cognomenlaw.com for a focused second read.

How does the .jp route compare with UDRP and court action?

The right route depends on the zone, the goal, and the registrant's conduct. Four situations illustrate the principal choices:

If the cybersquatter holds both a .jp and a .com targeting your brand, the JP-DRP addresses the .jp and the UDRP – at WIPO or the Forum – addresses the .com. The two proceedings can run in parallel. A favorable JP-DRP decision does not bind the UDRP panel, but it can be cited as persuasive evidence that the registrant has a documented pattern of targeting your mark. Filing sequence matters: a first favorable decision creates a record; the second benefits from it.

If the domain is a new-gTLD string (a .tokyo or .nagoya, for example, rather than .jp itself), the UDRP governs those zones, and the URS – the Uniform Rapid Suspension procedure – is available as a faster, lower-cost suspension remedy, though URS does not transfer ownership. See our companion guide on suspending a domain through URS for that route.

If the brand owner also wants monetary damages – not just the domain – neither the JP-DRP nor the UDRP can deliver them. Both procedures are limited to transfer or cancellation. A court action in the relevant jurisdiction, handled with local litigation counsel, is the only route that reaches a damages award. Court proceedings are substantially slower and more costly than administrative proceedings, and they are worth considering where the harm is quantifiable and significant, or where the registrant's conduct crosses into broader unfair competition or trademark infringement that a court can address comprehensively.

If the registrant holds domains across many zones – .jp, .com, .net, and several ccTLDs – a portfolio strategy is more efficient than piecemeal filings. We regularly advise brand owners on prioritizing a multi-zone recovery campaign: which domains carry the highest traffic risk, which zones have the most favorable procedural rules, and which can be consolidated into a single complaint.

For a full comparison of recovery routes across gTLDs and ccTLDs, see our main UDRP recovery service page.

What evidence actually decides a serial-cybersquatter JP-DRP case?

Evidence is the difference between a complaint that reads strong and a complaint that is strong. Panels decide on the record as filed; there is no discovery, no oral hearing, and in most cases no second bite. The serial-cybersquatter record is uniquely powerful when it is complete and organized – and uniquely vulnerable to dismissal when it is gestured at rather than proven.

The evidence bundle for a serial-cybersquatter JP-DRP case should contain, at minimum: the trademark registrations or use evidence establishing rights (with dates); WHOIS/RDDS records for the disputed .jp domain, including historical records showing original registration date; WHOIS records for each additional domain in the serial pattern, organized with a brief annotation identifying the third-party brand targeted; screenshots of the disputed domain's current and historical resolution (including Wayback Machine captures); any correspondence between the registrant and the complainant – particularly any buy-back demand, which is itself a bad-faith indicator under Paragraph 4(b); and any prior dispute decisions naming the registrant, even in other zones, that establish the pattern on the record.

Do not omit the buy-back demand correspondence. A demand for a price exceeding the registrant's out-of-pocket registration costs is explicitly listed as a bad-faith indicator. Many brand owners hesitate to disclose their own communications because they contain internal valuations or negotiating positions. The relevant document is the registrant's demand, not the brand owner's response. Submit the demand.

In a recent matter (a .jp domain targeting a European consumer brand, spring 2025), the registrant had sent a demand through an intermediary using deliberately vague language to avoid appearing to be a direct ransom demand. We submitted the full chain of communications. The panel found that the indirect framing did not change the commercial reality: the registrant had no legitimate use and was holding the domain for sale to the mark owner at a price beyond cost. Transfer was ordered.

Related at COGNOMEN

• UDRP domain recovery: the full service for gTLD complainants
• Recovering a domain from a passive-holding registrant
• How to suspend a new-gTLD domain through URS