Moniker.com Launches Domain MaxLock™

2008 September 23
by Michael H. Berkens

Moniker announced today Domain MaxLock™, a product designed to safeguard valuable domain assets from costly employee errors or malicious cyber attacks.

MaxLock will prevent Unauthorized transfers, often times a result of shared accounts, employee errors, high-jacked email accounts, automated transfers or pushes by domain marketplace distribution networks.

Unlike a standard registrar lock, with MaxLock™, domain assets cannot be transferred or pushed to another account without a thorough off-line validation and account verification process performed by the Moniker security team.

Monte Cahn, head of Oversee’s Aftermarket and Registrar Division, said “Safety for domain assets is critical, and MaxLock™ is the best service available for anyone who wants iron-clad protection for their names.,

For more information about the product, visit www.domainmaxlock.com and contact Moniker at sales@moniker.com, or call 1-800-841-7686.

4 Responses leave one →
  1. 2008 September 24

    Well done Moniker – Perfect – I hope other domain name registrars follow moniker.

    Secure the owners Internet Real Estate

  2. 2008 September 24

    Sounds like this should’ve been a standard option. Seems to me it’s kinda like going to the car wash and paying extra for soap.

  3. 2008 September 24

    Any difference between this and the Fabulous.com Executive Lock?

  4. 2008 September 24
    Fellow David permalink

    Sounds like this should’ve been a standard option.

    It’s nice if they do. But their new MaxLock™ requires both online and offline verification, which takes some time and effort.

    While one can argue how “simple” it is to do that, others can argue one should be compensated somehow for their efforts. It depends on their business model.

    Then again, I can’t unlock mine so I guess I won’t need it for now. :D

Leave a Reply

Note: You can use basic XHTML in your comments. Your email address will never be published.

Subscribe to this comment feed via RSS

Please copy the string rHELa1 to the field below: