Practical guide

Domain ownership audit guide

Audit client-domain ownership without conflating the registrant, registrar login holder, agency operator, and renewal decision owner.

By OpsBlip editorial team · Reviewed July 15, 2026 · Every 90 days or when transfer policy changes review

The outcome

‘We manage it’ is not an ownership record. This audit separates four roles so a technical operator does not accidentally become the assumed legal owner or approver.

Workflow

1.Start with the client’s portfolio, then mark every domain as confirmed, conflicting, or unknown rather than filling gaps with assumptions.
2.Compare registrant information, account control, billing responsibility, and renewal approval authority as separate evidence fields.
3.Escalate conflicting or unknown records to the client decision owner with a deadline and a written question.
4.Re-audit after account changes, a registrar transfer, an agency offboarding, or any material ownership change.

Ownership audit row

Adapt this to the client’s actual authority and records; do not put passwords, tokens, recovery codes, or private keys in it.

Domain: example.com
Legal registrant: confirmed | conflicting | unknown
Registrar account controller: confirmed | conflicting | unknown
Billing / renewal payer: confirmed | conflicting | unknown
Decision authority: name / role / evidence
Last verified: YYYY-MM-DD
Gap owner and due date: [person] / [date]

Product CTA

OpsBlip’s current build is designed around accountable domain records, renewal decisions, client approvals, and handoff packs. Public production availability is not verified.

See the planned workflow

Sources and limits

External facts on this page are limited to the sources below. Product-specific details not stated by a source are marked unknown and should be confirmed with the provider.

ICANN Transfer Policy