Agency Client Handoff
Keep client domains launch-ready without owning every registrar account.
Use this when an agency manages domains for multiple client sites, campaigns, or product launches.
What this solves
- You can audit domain readiness before launch.
- Clients can keep domains at their registrar.
- Renewal, DNS, SSL, and nameserver risks are visible during handoff.
- Registrar access can use API credentials instead of shared passwords.
Client onboarding checklist
- Ask the client which registrar owns the domain.
- If the registrar is supported, have the client create API credentials for that registrar.
- Connect the registrar in Domain Collective.
- Confirm the domain appears in the dashboard.
- Review expiry date, auto-renew status, nameservers, DNS records, and SSL status.
- Fix launch blockers before changing production DNS.
- After launch, run a manual sync and confirm the dashboard matches the registrar.
Handoff checklist
Before handoff, capture:
- Registrar name and account owner.
- Renewal date and renewal status.
- Current nameservers.
- Production DNS records.
- SSL status.
- Any registrar sync warnings or unsupported operations.
Registrar recommendations
- For new client domains, Spaceship and Porkbun are fast to connect because they do not require IP allowlisting.
- Namecheap can work well, but the client must allowlist Domain Collective's static IPs before the API connection works.
- GoDaddy may require API eligibility depending on the client's account.
FAQ
Does the client need to transfer the domain to us?
No. The client can keep ownership at their registrar while giving the agency operational visibility through an API connection.
Should we ask clients for registrar passwords?
Avoid that. Ask for scoped API credentials when the registrar supports them.
What if the client uses an unsupported registrar?
Use the supported registrar matrix to choose the closest workflow, or request the registrar from the dashboard.
What should we check right before launch?
Confirm nameservers, required DNS records, SSL status, and renewal safety before switching production traffic.
Last verified: June 2026