The Internet Corporation for Assigned Names and Numbers (or ICANN for short), recently introduced some new requirements relating to how domain renewals should be handled by domain registrars. This is a binding, contractual obligation that all registrars must comply with.
As of today, we have implemented some new functionality into our cleitn area to now fully and automaitcally comply with this requirement. We have always sent domain expiry warning notices at regular intervals within the 30 days deading up to the expiry of a domain name. One of the new requirements from ICANN is that if a domain expires, the registrar must send at least one post expiry notice within 5 days of the expiry date which we were also already compliant with.
Another new ICANN requirement was that it is no longer sufficient to just send the expiry notice to a domain's registered account holder (ie our client area account holder), but rather it must go to the email address listed under the registrant contact of the whois record. We now perform this for all non .uk domains, sending it to both the account holder and the registrant contact (if they differ).
Lastly, ICANN now requires sufficient logging of the domain renewal notices so that an audit trail can be provided for regulatory compliance. With that being said, we now have a new dedicated logging system for domain renewal notices which will keep a log of all renewal notices that are sent, along with the date and recipients, and provide an easy way to view and export that information upon request from ICANN so as to be able to prove compliance.
The only real change therefore from this new requirement is that the registrant address must now be e-mailed with a renewal notice. If you are registering e-mails for a client in the capacity of a reseller, you may therefore wish to take note of this as e-mails will be sent directly to the registrant e-mail address on record at the registry as is now required.
Details of ICANNs policies can be found here: https://www.icann.org/resources/pages/errp-2013-02-28-en
jeudi, février 26, 2015
Powered by WHMCompleteSolution
