Feature Requests
Share ideas, discuss and vote on requests from other users in community

Improving ID Protection Feature

Zach Lewis shared this idea 5 years ago
Under Consideration

As I started to do major redesigning of the WHMCS theme, I’m testing a lot of features and noticing they are frustrating and don’t work correctly.

Here’s a couple thoughts on improving ID Protection:

1. Enom offers free ID Protection, so if we want to extend that offer to our customers they can’t do a simple enable/disable. They have to go through a useless invoicing step.

2. A single ID Protection plan shouldn’t be tied to a domain. It would be ideal if clients purchased ID Protection plans and they were able to enable, disable and even assign that plan to another domain. Right now, the system ignores the originally purchased ID Protection and forces them to purchase another plan, even though the first one wouldn’t technically be expired. Another point is that if a client disables it unknowingly, they would have to pay to re-enable it.

3. Upon doing a transfer, the system pulls the WHOIS information from the old domain host that is often times a WHOIS privacy plan. So, when a client enables ID Protection with us, they are simply masking outdated WHOIS privacy information from the old domain host. You could confirm with client that the information on the domain is updated during the transfer process?

I’m not sure the possibility of doing these things. I do know that Namecheap is a reseller of Enom and they do ID Protection plans like I explained and I've never had issue with getting the correct information upon transfers.

Comments (7)


As a VAR, I would also like to see the ability to add custom domain addon options, just as I can do custom hosting addons.


Since when does eNom offer free WHOIS privacy?


We need to allow to place order for ID protect Addon from WHMCS client area >> domain >> domain addon

Currently ID Protection would not automatically be added to eNom domains when

ordered after domain registration, your staff would need to do this

manually via the eNom website.

Only when ID Protection is selected at registration/renewal time would it be added to the domain automatically by WHMCS.


+1 Improved ID Protection Handling

Enom does charge for ID Protection.

At this time, there is no indicator (TODO Item or otherwise) that manual

intervention is required to keep ID Protection enabled. Many customers

may not have the ID Protection that they are paying for. This requires

us to run manual DB queries and cross-check across 100's if not 1000's

of domains to ensure the customer has what they actually paid for.


Protection as an addon needs to have it's own billing cycle in

years ( much like a hosting product Addon ), with invoicing

specifically related to this add on, and automation to purchase the

protection after domain registration. Including a ToDo item when manual

intervention is required.

At Enom, ID Protection is associated directly to the domain purchased and is not transferrable. ID Protection also has it's own billing cycle ( if added after the initial registration ) and can only be added one year at a time. Unless the domain is set to "AUTORENEW" inside the Enom interface, you will have to manually add ID Protection once per year for the duration of the term that the client has renewed their domain.

We really need some help in this department. Marketplace modules? Core WHMCS development?


Any movement on this? This is a no-brainer


I need this. Any update? We have to do it manually and it really defeats the purpose.


As others have mentioned, when a customer orders the ID Protect feature at the time of domain registration, it all works perfectly (ID Protect is properly ordered via eNom and all is well). However, if the customer decides to add ID Protect sometime after the domain registration (where it's a day later, or months/years later) then this is the problem. WHMCS literally does NOTHING but take the customer's money. It does not order ID Protect from eNom. It does not create a TO-DO item for the hosting customer. It does NOTHING. This is really a problem.