FAQ: run due diligence before buying a .dev domain

What does it mean to run due diligence before buying a .dev domain?

Due diligence before buying a .dev domain means a structured legal review of everything that could make the domain a liability after the transfer – conducted before you commit funds. The .dev zone is a generic top-level domain operated under ICANN's accreditation system, which means the UDRP applies in full. A domain that attracted a prior dispute, was transferred in suspicious circumstances, or strings together a registered trademark is a domain that could land you in a proceeding you did nothing to cause.

In our practice, we see buyers focus almost entirely on the name's commercial value and overlook the chain of title entirely. The registration history matters. A domain that has changed hands three times in eighteen months, or that was previously suspended following a UDRP complaint and then re-registered, carries a documented record a panel will read. Buying it does not reset that record. You inherit the history, and the panel will read it alongside your conduct.

Due diligence for a .dev domain specifically covers five areas. First, WHOIS and RDDS verification – confirming the seller is the actual registrant of record, not a reseller acting without authority. Second, registration-date and expiry checks – a domain that is close to expiry presents transfer-timing risk. Third, prior dispute screening – a search of WIPO's online case database for any complaint filed against the domain or any confusingly similar string. Fourth, trademark conflict analysis – a cleared name today can become a contested name tomorrow if a pending application matures. Fifth, escrow structure – using a recognized third-party escrow service so that the registrar transfer and the payment release happen simultaneously, with neither side exposed.

One .dev-specific factor deserves attention. Google Registry enforces HTTPS-only access for all .dev domains at the registry level. That technical requirement does not affect the UDRP analysis, but it does affect how the domain is used in practice and what counts as active use versus passive holding. Passive holding of a .dev domain – pointing it at a blank page – can still be relevant to a bad-faith inquiry if a complaint is later filed against the buyer.

How long does it take to run due diligence before buying a .dev domain?

A standard pre-acquisition review of a single .dev domain typically takes between five and ten business days, depending on the complexity of the trademark environment and the depth of the registration history. That window covers WHOIS verification, a prior-dispute screen, a trademark clearinghouse check, and a legal assessment of any flagged conflicts.

Where the name is short, generic, or dictionary-based – the kinds of .dev strings that attract the most buyer interest – the trademark screen is usually straightforward. Where the name is a brand-adjacent string or a slight variant of a known mark, the analysis takes longer because multiple classes and jurisdictions may be relevant. In those cases, a buyer is better served by a broader clearance review than a fast one.

The timeline for escrow structuring runs in parallel, not in sequence. Once the legal review flags no material risk – or identifies risks the buyer accepts – the escrow arrangement can be set up and the registrar transfer initiated. From a purely technical standpoint, a registrar transfer for a .dev domain operates under the standard five-to-seven-day registrar transfer window. Legal due diligence should be completed before that window opens, not during it.

Can due diligence be rushed? It can be compressed to two or three days for a straightforward name with a clean record and no trademark conflicts in the relevant classes. We do not recommend compressing the trademark screen, however. A pending application that matures into a registration after the deal closes can still support a UDRP complaint, and the filing date of the application – not the registration date – is what the panel will look at when assessing priority.

For an assessment of your domain transaction and the due diligence it requires, contact info@cognomenlaw.com.

What does it cost to run due diligence before buying a .dev domain at WIPO?

Due diligence is a pre-purchase legal service, not a WIPO filing – so there is no WIPO fee for the review itself. The cost of due diligence is a legal-service fee charged by counsel, separate from any forum fees that would apply only if a UDRP complaint were filed after the acquisition.

For context on what a dispute could cost if due diligence is skipped: the WIPO filing fee for a UDRP complaint covering one to five domains before a single-member panel is USD 1,500. A three-member panel at WIPO costs USD 4,000. Those are the fees the complainant pays – but they define the forum cost environment in which a tainted domain could be challenged. Defending such a complaint as a respondent involves comparable legal-fee exposure.

Legal fees for a due-diligence review vary by scope. A single-domain review of a .dev name with a clean record is a contained engagement. A portfolio review, or a review involving a contested name with prior dispute history, requires more analysis and costs accordingly. Market rates for this type of work sit in a range that is materially lower than the cost of defending an unwinnable UDRP complaint after the fact.

The honest framing: due diligence is insurance. You are paying a fraction of what a defended UDRP respondent proceeding costs, in exchange for knowing before the transfer whether the domain is worth acquiring – and on what terms. Pricing transparency is something we practice at COGNOMEN. We provide written scope and fee estimates before any engagement begins, not after.

What evidence is needed to run due diligence before buying a .dev domain?

The evidence a buyer needs to assemble – and that counsel needs to review – falls into two categories: seller-side documentation and third-party public records.

From the seller, a buyer should obtain the current WHOIS record confirming registrant identity, proof of the registration date, any transfer history the seller can document, and confirmation that no payment or settlement agreement is outstanding from any prior dispute. If the seller acquired the domain from a third party, that prior acquisition should be documented as well. A gap in the chain of title is itself a finding.

From public records, counsel screens the WIPO UDRP case database for prior complaints naming the domain or the registrant. The WIPO database is publicly searchable and a reliable source for this inquiry. Trademark searches in the relevant classes and jurisdictions round out the record. For a .dev domain – which is developer-ecosystem adjacent – relevant trademark classes often include software, technology services, and communications, but the brand-specific analysis varies by name.

One piece of evidence buyers frequently overlook is the domain's historical DNS and use record. A domain that previously resolved to a parking page monetizing competitor trademarks carries a use history that a future panel could weigh, even after a legitimate buyer acquires it and puts it to a clean purpose. That history does not evaporate on transfer. Reviewing archived DNS records before closing is a standard step in a proper due-diligence engagement.

What evidence is not needed at the due-diligence stage? You do not need to prove your own trademark rights to run a pre-acquisition check. Due diligence is a risk-assessment exercise, not a claim. The analysis is about what a potential complainant could prove – not about what you can prove – so the framing is adversarial from the outset.

Can I run due diligence before buying a .dev domain for more than one domain at once?

Yes. Portfolio due diligence – a coordinated review of multiple .dev domains in a single engagement – is efficient and is how most technology-sector buyers approach acquisitions involving more than two or three names. The mechanics are the same for each domain; the efficiencies come from shared trademark research and batched WHOIS and dispute screening.

There is a practical limit, however. A portfolio review of ten or fifteen .dev domains with varied trademark exposure is not the same exercise as a single-domain check. Each domain requires its own conflict analysis; a clean finding on one name does not carry over to another, even if the names are thematically related. Where a portfolio spans multiple registrars or involves domains with different expiry timelines, the coordination of escrow and transfer logistics also requires planning.

UDRP complaint mechanics offer a useful parallel here. Under the UDRP, a single complaint can cover multiple domains only if they share the same registrant. Due diligence does not have that constraint – a buyer can review as many names as needed in a single engagement regardless of how many sellers are involved. But the analysis is individuated per name.

In a recent engagement (a portfolio of .dev and .tech names, spring 2025), we screened approximately a dozen domains for a software-sector buyer before a bulk acquisition closed. Two names were flagged as carrying trademark conflict risk in a core class; the buyer renegotiated terms on those two names specifically and proceeded with the clean remainder. That outcome – a targeted risk adjustment rather than a wholesale withdrawal – is what a properly scoped portfolio review makes possible.

To weigh UDRP against a court action for your case, or to plan a portfolio due-diligence engagement, email info@cognomenlaw.com.

What are the possible outcomes when you run due diligence before buying a .dev domain?

Due diligence produces one of four practical outcomes, and understanding them in advance shapes how a buyer should structure the acquisition.

The first outcome is a clean finding. The domain has no prior dispute history, no apparent trademark conflict, a clear chain of title, and no material risk factors. The buyer proceeds with confidence and the escrow closes normally. This is the most common outcome for generic and descriptive .dev names with no brand adjacency.

The second outcome is a conditional finding. The review identifies one or more risk factors – a pending trademark application in a relevant class, a prior WHOIS privacy change that clouds the registration timeline, or a domain that previously resolved to a parking page with potentially infringing content – but the risks are manageable. The buyer can address them through price negotiation, a warranty from the seller, a holdback in escrow, or simply an informed decision to accept the risk. What distinguishes this from skipping due diligence entirely is that the buyer knows what they are accepting.

The third outcome is a flagged finding with a recommendation against proceeding. Some domains carry risks that cannot be mitigated by deal structure. A domain that is the subject of an active UDRP complaint – or that is so confusingly similar to a well-known registered mark that a complaint is effectively inevitable – is a domain that a buyer cannot safely acquire at any price. The due-diligence engagement preserves the buyer's funds and avoids a losing respondent position.

The fourth outcome is a finding that redirects strategy. Due diligence sometimes reveals that the domain a buyer wants is not the right acquisition – but a related name is. A .dev string that carries a trademark conflict might prompt consideration of an alternative string, a different zone, or a direct approach to the trademark holder about a license arrangement rather than a secondary-market purchase. That strategic redirection is only possible if the review happens before closing.

What due diligence cannot do is guarantee a conflict-free future. Trademark filings are filed every day. A name that is clear today can face a challenge tomorrow if a new application matures into a registration with an earlier priority date. Due diligence is a snapshot as of the review date, not a permanent clearance. Ongoing brand-protection monitoring after acquisition is the complement to pre-purchase review.