Domains & Authentication
Domain already registered by another account
Resolve the 403 “domain already registered” error by confirming domain ownership and account access, and requesting a release if needed.
Overview
When you add a domain to SendPing, you may see this error: The example.com domain has been registered already.
This means the domain is currently associated with a different SendPing account. A domain can only be active on one SendPing account at a time.
This is a
403 error — SendPing refuses to register the same domain twice across accounts to prevent two parties from sending as the same identity. The fix is to find and release it from the account that already holds it, not to retry the request.Why this happens
- A team member or contractor added the domain to a separate account.
- You are logged into a different account than the one where the domain was originally added.
- A previous trial or workspace of yours still holds the domain.
How to resolve it
- Check with your team. Ask whether anyone is already using SendPing and may have added the domain under their own account or a shared workspace.
- Confirm you’re in the right account. Make sure you’re logged into the account (and workspace) where you expect the domain to live, then look for it under Managing domains.
- Request a release. If you still cannot locate the domain, contact SendPing support and share the domain name so the team can verify ownership and release it so you can re-add it.
Once the domain is released from the other account, re-add it under your account and publish the DNS records SendPing generates — see DNS records — then re-verify the domain.