The person presenting an offer, the public registrar and the party authorized to sell are not necessarily the same. Verification should establish the role relevant to the transaction rather than substitute whichever name is easiest to find.
Separate public data from private authority
A registration lookup may identify a registrar while redacting registrant details. That is not permission to invent an owner or treat the registrar as the seller.
A live website can identify an operator without proving registration control or authority to transfer the domain.
Use the agreed transaction process
Ask how the marketplace, registrar or transaction service verifies the party delivering the asset. Confirm the exact domain and receiving account through genuine provider channels.
Do not send passwords or authorization codes to an unfamiliar correspondent simply because they request "proof." Verification should follow an authorized process appropriate to the provider and transaction.
Evaluate evidence by what it proves
A screenshot can be outdated or incomplete. A temporary DNS change may demonstrate some operational access without resolving all legal authority questions. A payment receipt establishes a payment event, not necessarily domain delivery.
Document unresolved questions
Record who is responsible for resolving authority, asset scope and delivery concerns. For material or disputed transactions, obtain appropriate professional advice rather than treating an automated lookup as sufficient.
Use Domain Lookup for public context and transaction verification for the wider evidence chain. WebOneWord does not authenticate private holders or guarantee that a listed seller can complete a transaction.
Sources and further verification
Policies and service conditions can change. Follow the primary source before a transaction or technical change.
Maintained by WebOneWord Team. Last reviewed: 2026-10-07.