Enom now requires both sender & receiver to create request in order for domain to be pushed

Every now and then it seems registrars are coming up with tough measures to make it difficult to effect a smooth domain sales, just don't know why.

Co-ordinating with support each time for a push would surely be a mess.

Nikhil Jain said:

Co-ordinating with support each time for a push would surely be a mess.

Click to expand...

keston57 said:

Every now and then it seems registrars are coming up with tough measures to make it difficult to effect a smooth domain sales, just don't know why.

Click to expand...

What is more surprising is that even domain receiver needs to create a request.

For now, as far as I know at namesilos the process is fairly smooth and straightforward.

OP thanks for the info

I just ran into this same message from enom today. There has been no notice of this change by enom so I contacted support to let them know of my desired future push of my property to another account at enom. I still have to wait for the other party to contact enom's (Tucow's) support to authorize the acceptance of the domain name into their account!

This new procedure has added another few hours to every transfer between accounts at enom. Plan your days accordingly. It's much easier to transfer out to another registrar that doesn't play games.

After a 60% surprise increase in renewal rates, it's only a few more months before the last of my domain names are removed from this atrocious registrar.

singhhooda said:

Hello Everyone

When some one tried to push domain to my enom account, they received an error :
One or more domains did not successfully push.
Error: does not have access control setup to allow pushes to. Contact Technical Support to setup Access ControlBack

So I contacted support and I was surprised to know their new rules.

Now we need to follow this : https://help.enom.com/hc/en-us/articles/360007349412-Enabling-Domain-Pushing (Check article shows today as Updated 2 days ago)

Both the resellers parties (sender/receiver) need to create verified support request in order to send and receive the domain push at enom.

Assuming A is sender and B is receiver, so both need to follow :

Sender A : "please enable push from my account "A" to allow push to "B""
Receiver b (Gaining account) : "please enable push on my account "B" to allow pushes from "A""

This will slow down the process and I think it will be more work for both the parties to get involved for just pushing the domain.

How you see this change?

Kind Regards,
Hooda

Click to expand...

Yes you have to set this up, but only once. Once you do this you will be able to push and receive pushed domains always. It is not as if you have to do this for every transaction.

mitch007 said:

Yes you have to set this up, but only once. Once you do this you will be able to push and receive pushed domains always. It is not as if you have to do this for every transaction.

Click to expand...

How is that going to be a one time setup if each recipient/receiver of a domain name push needs to contact enom support to let them know - in advance - that they will accept each domain name push?

Today, I was able to contact support to get them to expedite the push without the receiver's advance written acceptance but I spent more than 30 minutes out of my day waiting for a rep, chatting online, filling out a separate verified support request and then verifying the push. Time is money and this procedure is wasting both.