The current push system these companies (these three were the first I thought of, there may very well be several more) have is, quite frankly, nothing short of dangerous.

Why? Simply because only ONE field must be entered for a push to take place.

For Enom, you enter the recipient’s ID when pushing and bam, that’s it.

Same for NameCheap, same for Moniker.

But what happens if you make a mistake?

For example, let’s assume someone’s Moniker ID is 12345678, what if you type in 12345679 by mistake? Well, you might have just given one lucky person (the 12345679 account holder) a very expensive gift.

Or what if someone’s NameCheap username is “Alex” and you accidentally typed in “Alec”? Well in that case again, mr. Alec (I’m sure someone with a NameCheap account called “Alec” exists) will be receiving an early Christmas gift. Now sure, for less common usernames, the risk is a LOT lower. For example, nothing will most likely happen if instead of sending to “MyNameIsBillyJohnson” you send to “MyNameIsBillJohnson” (Bill instead of Billy) because the likelihood of an account with the mistyped name existing is very very low.

… I’m sure you get the point.

I don’t understand why they don’t ask for another data point, it’s not rocket science!

For example, when pushing a domain over at GoDaddy, you’re asked for two things:

1) the recipient’s email address
2) the recipient’s username or ID

… that’s it, problem solved.

Therefore, even if you make a mistake when it comes to one of the fields, you have absolutely nothing to worry about.

Fixing this doesn’t involve huge costs, it simply involves a small dose of common sense.