Recover control of an organization domain: build an evidence brief

Describe the reported problem without deciding the rights

Start with one factual sentence: which organization reports which access or control problem, when it was noticed and who can provide the original observation. Distinguish a failed login, inaccessible recovery email, changed registration data, suspected registrar move and disputed entitlement. Several may coexist, but each needs its own supporting record. Do not convert “a contractor used to manage it” into a theft allegation.

Name a coordinator and record the internal authority reference. That assignment permits only the work it actually authorizes; it does not create registrant rights or guarantee provider acceptance. Keep registration, registrar account, authoritative DNS, website host and mail administration separate. Access to one does not settle the others.

Begin with a blank control record

For every entry add source/time ____, authorized custodian ____, what is known ____, uncertainty ____ and next review ____. A claim and a verified fact should remain visibly different. These are planning fields, not a mandatory registrar form.

Leave unknown fields unknown. A public page or old receipt cannot fill in the current account holder by inference. Do not assume every registrant detail will be publicly visible; this guide performs no lookup and adopts no completeness promise from legacy WHOIS terminology.

Keep references and provenance, not private document copies

For each row note evidence locator ____, what it actually supports ____, custodian/authorized reader ____, availability/provenance gap ____ and question for the provider or qualified adviser ____. Keep sensitive proof in its approved private location.

Use references rather than copying IDs, signatures, credentials, authorization codes or payment data into a shared worksheet. Before an authorized submission, verify the responsible provider’s official channel and current requirements. A well-organized internal file is not itself proof that a recovery request qualifies.

Choose an evidenced branch with a stop condition

Add a named internal receiver ____, evidence to hand over ____ and next review ____ to the selected row. Provider-specific steps must be confirmed with the actual provider. GoDaddy’s public help illustrates distinct email-access, listed-registrant and verification situations; it does not establish a universal workflow.[1]

ICANN directs claimed unauthorized transfers to the previous registrar immediately and unauthorized registration-data changes to the registrar immediately. A possible reversal depends on circumstances and applicable law. Do not wait for this worksheet to become perfect before an authorized person raises an evidenced urgent incident through the genuine channel.[2]

Keep provider requirements and ICANN authority in scope

The GoDaddy page documents identity verification and business documentation when a company is listed in the account. It also notes high request volume. Read the current exact requirements in the provider’s official process; this guide supplies neither a universal sufficient-document list nor a response deadline. No reset, upload, verification cancellation or support request has been attempted.[1]

ICANN describes contractual authority, not power to return a domain directly or edit registration data. A contract or registrant dispute may require qualified legal advice; narrow trademark proceedings are not a general lost-login remedy. Keep this accredited-gTLD context distinct from country-code registry rules. No linked proceeding, full legal policy or actual entitlement is assessed here.[2]

Fictional Lantern Assembly: four records, no rights score

Two available + one pending + one missing = four references. This is an availability count, not ownership confidence, evidence sufficiency or recovery probability. Current registrant and recovery-email access remain unknown. The coordinator prepares questions, not a reset, unlock, transfer or payment. An actual unauthorized transfer would select the previous-registrar incident branch; an entitlement dispute stays on its distinct contract/advice branch.

Separate a completed brief from recovered control

An internally complete brief identifies the claim, evidence limits, responsible provider, authorized coordinator, chosen branch and next unresolved gate. Actual recovery needs a real provider outcome and authorized organizational acceptance: what access or recorded control changed, who accepted it and what remains unresolved. A draft request, reference number or working website cannot stand in for that outcome.

Assign separate owners to service preservation and later account stewardship. Record only what they actually confirm, with a review time. Registrar transfer, renewal and cooperative agency handover remain separate plans. This guide provides no Boletolibre domain-recovery capability or successful recovery case.