ICANN Expired Registration Recovery Policy (ERRP)

A new Expired Registration Recovery Policy (ERRP) mandated by ICANN introduces consistency into expiration messaging and recovery for generic Top-Level Domain (gTLD) registrations across all ICANN-accredited registrars.

The following changes came into effect as a result of the new ERRP (for gTLDs only):

  • The 30-day expiration email notice is now MANDATORY. Resellers are no longer able to disable this message for gTLDs. You'll continue to be able to edit this message template as before.
  • A new, mandatory email has been introduced three days AFTER expiration. As with the pre-expiry emails, this message is editable by resellers.
  • ICANN requires resellers to publish fees for domain renewals, including post-expiration renewal fees (if different) and also redemption/restore fees on their website. Additionally, those fees must be included in registration agreements. All resellers are required to be in compliance with this by the end of August. (note: redemption and other fees are detailed in the Master Services Agreement in Appendix A -download as PDF)

To avoid any registrant confusion, the 30-day expiration email notice will not be sent for gTLDs set to auto-renew in OpenSRS.

The changes to email messaging went into effect on June 24, 2013. You may wish to verify that all of your message templates are as you want them. Assuming you are logged in, you can do that here: https://rr-n1-tor.opensrs.net/resellers/index.cgi?action=mspconfig_useremail

Frequently Asked Questions

Why are 30-day renewal reminders becoming mandatory?

ICANN has mandated that all registrars, including Tucows/OpenSRS, provide email reminders to registrants 30 days prior to expiry. Expired Registration Recovery Policy (ERRP)

Can I just handle the reminders myself and opt-out of the ones sent by OpenSRS?

No. ICANN requires that the emails be sent as a condition of our accreditation and we are subject to a compliance audit to ensure the emails were sent as required. Allowing resellers to opt-out is not possible as we can’t fully ensure compliance with the policy unless we are fully in control of the sending of the emails.

My system/panel handles renewals automatically, a few days prior to expiry. My customers will be confused if they get an email that tells them their domain will expire. What can I do?

Even if you have your own system that automatically renews domains prior to expiry, ICANN still mandates that emails be sent 30 days prior to remind registrants that their domains are coming up for renewal.

The emails sent by OpenSRS to registrants can be edited and customized with your own messaging via the Reseller Web Interface. We recommend that you take the opportunity to include any information about how you handle automatic renewals. Consider reminding your customers to ensure that their payment information is up to date to ensure the renewal is processed successfully. This both reduces any registrant confusion, and also assists in ensuring that renewals are more likely to occur without incident.

What if I set domains to auto-renew in OpenSRS? Does that disable the messages?

Domains set to auto-renew in OpenSRS will be renewed 30 days prior to expiry and therefore no notice will be sent. Auto-renew does not actually disable the messages. If we instead auto-renewed domains 10 days before expiry (or allowed resellers to choose a variable renewal date), then the 30-day notice would still have to be sent as mandated by ICANN.

Have more questions? Submit a request

9 Comments

  • Avatar
    Markus

    There is no 3 day after expiry template here yet which could be customized in advanced before the mails are starting to be sent:  https://rr-n1-tor.opensrs.net/resellers/index.cgi?action=mspconfig_useremail

    Hopefully the 5day prior expiry message becomes optional with the changes.

  • Avatar
    James Koole

    The 3-day post expiry message will show up once the code promotion happens on the 18th as it is a new message. It will be in Horizon on the 13th if you want to get your template text ready in advance.

    The 5-day message remains mandatory. The ICANN policy doesn't specify dates, but rather stipulates that the registrant must receive two notices prior to expiry and one within five days after expiry.

    2.1.1. Prior to the expiration of any gTLD registration, registrars must notify the registered name holder of the expiration at least two times. One of these notices must be sent approximately one month prior to expiration and one must be sent approximately one week prior to expiration.

    Hope that helps.

    James.

  • Avatar
    Liz Van Gerven

    Will there now be two 30-day options in the "Configure daily end user renewal reminder email" section?

    Meaning, one we can disable or enable for non-gTLDs (that we take care of ourselves) and another that we cannot disable for gTLDs under the new ICANN ERRP?

  • Avatar
    domain

    There still does not appear to be a place to edit/configure the new 3 day after expiry message. I assumed it would appear with the others by  (the previously extended date) June 20th, at this location:

    https://resellers.opensrs.net/resellers/?action=mspconfig_useremail

    Am I looking in the wrong location?

  • Avatar
    Markus

    something changed up above; The changes to email messaging will go into effect on June 18, 2013  June 24, 2013

  • Avatar
    James Koole

    domain - we could have better communicated the change in date. We had a bit of an issue rolling out the full release which includes the ICANN messaging changes so it's been pushed back until Monday, June 24th.

    Markus - thanks for helping out.

    James.

  • Avatar
    Markus

    I think the changes are live now. At least I can configure a 3 day after expiry message which doesn't seem to be optional. The template page still lets me select an optional 30 day before expiry message. It's not really clear that this message would be madatorly sent for gTLDs. Maybe that could be communicated on the https://rr-n1-tor.opensrs.net/resellers/index.cgi?action=mspconfig_useremail setting page. :-) (I guess it will allready tell you this if you read the manual)

    Also the changes don't seem to be rolled out to other OpenHRS Instances (namely resellers.resellone.net) as of writing this.

  • Avatar
    domain

    Yup changes are live now, I noticed it had been updated yesterday (24th) afternoon, and have tweaked the new 3 day after expiry message. Tx.

     

     

  • Avatar
    Markus

    Changes seem to have gotten roled out to the OpenHRS Instances now. At least for resellone/SoftLayer I can confirm this.

Please sign in to leave a comment.
Powered by Zendesk