A promising domain name invites quick judgments about length, spelling, and commercial appeal. Due diligence begins with a different set of questions: what exactly is being offered, who can authorize its transfer, what will it cost to keep, and what work or uncertainty comes with its history? A name can be appealing while the proposed acquisition remains poorly defined.
Use the domain name screening framework to organize the review. The objective is a written list of conditions that can be satisfied before completion. A checklist should help you distinguish an ordinary unanswered question from a missing fact that prevents a sensible decision.
Define the exact name and acquisition scope
Copy the complete domain, including its extension, into your record. Check spelling character by character. If the name includes internationalized characters, record the displayed form and the technical form used by the registrar. Ask another person to read it aloud and type it independently. Treat any confusing variation as a practical usability issue to investigate.
Write down what the quoted price includes. The domain alone, a functioning website, a logo, email accounts, customer information, and social profiles are separate items in an acquisition review. Do not let an attractive landing page imply that all of its components are included. For each additional item, request its own identification, transfer method, and supporting documentation.
Keep registration control, permission to use a brand, and ownership of creative work as separate questions. A registrar account view can help examine control of a registration; it should not be used as a substitute for checking the other rights your intended project requires. Define those requirements before assigning value to the package.
Establish who can authorize the transaction
Ask the seller to explain their relationship to the domain and their authority to arrange the sale. Is the seller the registrant, a company representative, or an intermediary? Where another party must approve the transaction, include that approval in the closing conditions. Match the contracting party with the party expected to deliver the asset.
Use an agreed verification method that does not require anyone to disclose passwords, recovery codes, or unrelated account information. A registrar walkthrough or a specifically arranged control demonstration may address part of the question. Record what was demonstrated, when, and by whom. A demonstration of technical control still leaves the contractual authority question to be addressed separately.
Confirm the transfer path before setting a deadline
ICANN's Transfer Policy distinguishes transfers between registrars from changes of registrant and sets requirements and restrictions for covered transfers. Use it as the primary reference for the relevant process, then obtain instructions for the specific registration from the registrars involved. Do not assume that every extension or every account change follows an identical route.
Ask which steps apply to the planned acquisition: an account move, a change of registrant, a registrar transfer, or a combination. Request confirmation of current transfer restrictions and their release conditions. Check the registration's expiry date against the proposed timetable. Keep policy requirements, registrar procedures, and the commercial agreement in separate fields so that one is not mistaken for another.
- Identify the current registrar and the intended receiving account or registrar.
- Confirm the required approvals and how the parties will receive notices.
- Document any lock, restriction, or pending issue affecting the planned route.
- Agree what evidence will show that delivery is complete.
- Specify how an unresolved transfer issue changes the timetable or closing decision.
A seller's proposed sequence deserves the same scrutiny as the asking price. If the name must support a launch by a fixed date, leave time to resolve discrepancies rather than building the whole plan around an unverified promise. A cheaper name that cannot meet the operating schedule may not satisfy the original requirement.
Separate acquisition cost from the cost of keeping the name
Build a cost record with distinct rows for the purchase amount, transaction costs, registrar charges, renewal, and any required supporting services. Ask for a current renewal quote for the exact domain and extension. Record the currency and the period covered. Treat an introductory registration price as evidence about that offer only until the ongoing terms have been checked.
| Cost question | Evidence to request | Decision use |
|---|---|---|
| What is paid to acquire it? | Written purchase terms and included assets | Define the initial commitment. |
| What is paid to retain it? | Renewal terms for the exact registration | Estimate continuing cost. |
| What is required to move it? | Transfer process and applicable charges | Budget the transition. |
| What is required to operate it? | Chosen DNS, email, and hosting requirements | Avoid omitting supporting work. |
Calculate a holding scenario over the period relevant to your project. State which costs are confirmed and which may change. If the acquisition depends on eventually selling the name, identify that as a separate assumption. An attractive purchase price is not evidence that another buyer will appear on your preferred timetable.
Investigate brand questions without jumping to legal conclusions
Describe the intended business activity, target markets, and proposed presentation of the name. Then search relevant official trademark records and examine existing uses that may overlap with that plan. Record the search terms, jurisdiction, date, and matches requiring further review. Include close spellings and pronunciation where they matter to the proposed brand.
Do not convert a quick search into a statement that a name is legally clear. If a relevant match, dispute, or objection appears, preserve the evidence and obtain qualified advice about the specific use before committing. The screening task is to surface questions for the appropriate reviewer. It is not to decide legal rights from a registration record or the absence of an obvious search result.
Read the domain's history as a sequence
Review available historical pages and build a brief timeline of uses. Note apparent topic changes, periods without usable records, unusual redirects, and any content that conflicts with the planned identity. Record observations with dates. An archive gap should remain a gap; it should not become a claim that the domain had no activity during that period.
Inspect the current destination and the pages that remain accessible. Ask the seller to explain material differences between the current presentation and the historical record. If the asking price relies on search visibility or links, use the separate domain SEO screening process. A brand assessment and a search history assessment answer different questions, even when they concern the same name.
Plan the handover as an operating change
List what must work immediately after delivery: account access, registration contact information, renewal settings, DNS control, and any included service. Decide who will check each item and preserve the relevant confirmation. Where a website or email service is included, identify dependencies before changing nameservers or moving accounts. The handover should have an explicit owner.
Review the terms governing payment and delivery before initiating either. Define the completion evidence, the response to a discrepancy, and any agreed support period. Where a transaction service is used, examine its actual terms and acceptance conditions. Its presence does not answer every question about asset scope, usability, or the parties' responsibilities.
Assign responsibility after completion
A domain review should name the person responsible for renewal and account recovery after handover. Confirm where notices will go and whether that address remains accessible if the domain itself stops working. Record the registration term and a review reminder in the operating calendar. These are continuing responsibilities that should have an owner before the acquisition is complete.
Keep sensitive account information out of the general decision sheet. The sheet needs to record that access and recovery were checked, who performed the check, and where authorized operators can find the approved procedure. It does not need to contain secrets.
Conclusion: close only the questions that are actually answered
Finish with a decision sheet showing exact identity, included assets, authority evidence, transfer route, continuing costs, history, and unresolved brand questions. Mark each condition as satisfied, pending, or a reason to stop. The evidence-first screening method is useful for keeping that decision traceable.
The strongest domain acquisition case connects the name to a defined purpose and a workable handover. It does not rely on the name's appeal to fill missing information. Once the required evidence and operating conditions are clear, you can discuss price with a more precise understanding of what you would receive and what remains your responsibility.
https://digitalassetscreener.com/blog/domain-name-due-diligence-checklist/
