DEV Community
Follow
The “Who Holds the Keys?” Audit: Mapping Registrar Account Ownership vs. Agency Operational Access
Client-agency offboarding often turns problematic due to confusion over domain ownership and technical access. Agencies sometimes register clients' domains in their own master accounts, leading to disputes when clients try to move providers. This issue stems from blurring the lines between who is named as the domain registrant and who controls the registrar account.The registrar account owner has ultimate control, including managing login credentials, payment methods, and obtaining transfer authorization codes. The registrant is the named holder of the domain, as per ICANN policy, but this doesn't guarantee account access. Technical administrative access, often granted to agencies, allows editing DNS records but doesn't confer account ownership or transfer rights.Historically, domains had multiple contacts, but now only the registrant is universally required for generic TLDs. Agency master accounts are high-risk because the agency holds the login and can withhold transfer codes. Best practice dictates a client-owned account with delegated, limited access for the agency.Custody battles frequently arise from onboarding shortcuts where agencies register domains quickly in their own accounts, never rectifying ownership. Other pitfalls include personal employee registrations tied to individual emails, and agencies reselling domains, making clients dependent on the agency for changes.A five-step audit framework helps clarify domain control. This includes checking registration data, mapping the registrar account owner, auditing multi-factor authentication and recovery channels, reviewing nameserver and DNS control, and ensuring contracts align with technical reality. Public WHOIS/RDAP data is often redacted, necessitating login to the registrar account for accurate registrant details.The audit identifies red flags like agency-owned account emails, personal MFA devices, or contracts silent on asset ownership. The goal is to ensure the client owns the registrar account, with the agency granted only necessary, limited access for tasks like DNS editing. This structured approach prevents digital asset hostage situations.