Do You Accept Push from Hosting Based Registrars
Seller Delivery Policy Clarification
Daaz Support
Last Update 7 months ago
Answer: No.
DaaZ does not accept internal push from certain hosting based registrars where domain control is bundled with hosting services or account level dependencies.
Why Hosting Based Registrar Push May Not Be Supported
Some providers primarily operate as hosting platforms rather than domain focused registrars. In certain cases, domain control may be tied to hosting plans, bundled billing, or service restrictions.
Examples where push limitations may apply:
• HostMonster
• FastHosts
• Bluehost
• HostGator
• iPage
• JustHost
• IONOS
• Mandatory hosting linked account setup
• Service bundle dependencies
• Buyer account creation friction
• Administrative restrictions during push
• Delivery delays
Important Clarification
Not all hosting providers are restricted.
If a registrar allows clean domain only management without forcing hosting purchases or bundled services, push may still be supported.
Each registrar workflow is evaluated based on buyer convenience and operational clarity.
What Sellers Should Do
If push is not supported at your registrar:
When inter registrar transfer is required:
• Sellers must wait until transfer completion
• Payout is processed after successful transfer
• Delivery timelines may exceed standard SLAs
Please initiate transfer promptly after sale confirmation to avoid delays.
Our Principle
DaaZ supports delivery methods that:
• Protect buyer convenience
• Maintain independent domain control
• Avoid forced hosting dependencies
• Ensure predictable ownership transfer
If a delivery method creates avoidable friction, it is not supported.
DaaZ does not accept internal push from certain hosting based registrars where domain control is bundled with hosting services or account level dependencies.
Why Hosting Based Registrar Push May Not Be Supported
Some providers primarily operate as hosting platforms rather than domain focused registrars. In certain cases, domain control may be tied to hosting plans, bundled billing, or service restrictions.
Examples where push limitations may apply:
• HostMonster
• FastHosts
• Bluehost
• HostGator
• iPage
• JustHost
• IONOS
• One.com
• Mandatory hosting linked account setup
• Service bundle dependencies
• Buyer account creation friction
• Administrative restrictions during push
• Delivery delays
Important Clarification
Not all hosting providers are restricted.
If a registrar allows clean domain only management without forcing hosting purchases or bundled services, push may still be supported.
Each registrar workflow is evaluated based on buyer convenience and operational clarity.
What Sellers Should Do
If push is not supported at your registrar:
- Unlock the domain
- Obtain the authorization code
- Initiate a standard inter registrar transfer to DaaZ
When inter registrar transfer is required:
• Sellers must wait until transfer completion
• Payout is processed after successful transfer
• Delivery timelines may exceed standard SLAs
Please initiate transfer promptly after sale confirmation to avoid delays.
Our Principle
DaaZ supports delivery methods that:
• Protect buyer convenience
• Maintain independent domain control
• Avoid forced hosting dependencies
• Ensure predictable ownership transfer
If a delivery method creates avoidable friction, it is not supported.
