Personal tools

From HEXONET Wiki

Revision as of 00:20, 26 July 2013 by WikiAdmin (Talk | contribs)

Jump to: navigation, search

ERRP - Expired Registration Recovery Policy

The Expired Registration Recovery Policy is intended to help align registrant expectations with registrar practices by establishing certain minimum communications requirements and making renewal and redemption of registrations uniformly available in prescribed circumstances. Essentially, formalizing the process of renewal and redemption for all gTLDs.

Rational for the ERRP Policy

  • To help prevent unintended non-renewal of domain name registrations, registrars will be required to notify registered name holders of the expiration of their registrations at least two times: approximately one month prior to the expiration date and, again, approximately one week prior to the expiration date.
  • All gTLD registries must offer a Redemption Grace Period of 30 days immediately following the deletion of a registration. (Sponsored gTLDs are exempt, and not required to offer a Redemption Grace Period.) During the Redemption Grace Period, the registrant must be permitted by its registrar to restore the deleted registration.
  • To promote consumer choice and awareness, registrars must make their renewal and redemption fees reasonably available to registered name holders and prospective registered name holders at the time of registration of a domain name.
  • As in the past, registrars may delete registrations at any time after they expire, subject to applicable consensus policies and provisions of the Registrar Accreditation Agreement. However, the ERRP requires that resolution of the domain name be interrupted for a period of time after expiration, but before deletion, of the name to help make the registrant aware of the expiration of its name. Additionally, any parking page hosted by the registrar at the expired domain name must include or point to renewal instructions.

ERRP For Resellers

  • All required ERRP notifications must be sent out from the Registrar of Record, therefore, notifications will use the generic email address of [email protected].
  • Resellers can brand these notifications for their own customers through the Control Panel (see Notification Branding below)
  • Resellers ARE REQUIRED to clearly display Renewal and Restoration information on their websites, including information about ERRP renewal notices and how ERRP notices will be delivered (see Resellers Terms of Use below)
  • Resellers are REQUIRED to clearly display Registrant renewal pricing, restore pricing (Renewal Grace Period (RGP)) fees and how to access renewal/restore information - meaning that resellers must post renewal and restore fees on their pricing page as well as link to these prices in their own terms of use.



HISTORY
At the request of ICANN's At-Large Advisory Committee, on 5 December 2008, ICANN published an ISSUES REPORT on the topic of Post-Expiration Domain Name Recovery. The Generic Names Supporting Organization Council ("GNSO") initiated a Policy Development Process in May 2009, which resulted in the submission of several policy and process recommendations to the ICANN Board of Directors. The ICANN Board adopted the policy recommendations on 28 October 2011, and directed ICANN staff to implement this policy.

A period for public comment on the Expired Registration Recovery Policy opened on 11 October 2012 and closed on 18 November 2012. The period for reply opened on 19 November 2012 and closed on 7 December 2012. ICANN has reviewed the comments submitted, and where appropriate, incorporated suggested modifications into the Expired Registration Recovery Policy.


Resellers are able to brand the ERRP notifications through HEXONET's Control Panel. The instructions are as follows:

  • Login to the Control Panel and navigate to MANAGE ACCOUNT > MY SETTINGS > DOMAIN SETTINGS > ERRP EMAIL SETTINGS
  • Configure the following fields and these values will be automatically inserted into the ERRP notifications for the Reseller's customers. 
* Company Name - provide the company name to be used in the email
* Telephone Number - for a support or a customer service number
* Support Email Address - for a direct email link to your support
* Legal URL - a link to your Terms of Use or another legal page
  • IMPORTANT - there is no "FROM" email-address option since ERRP notifications must be sent out and addressed by the Registrar of Record according to the ICANN policy
  • Resellers who choose not to configure any of the optionally branding fields, your clients will see a generic email without names, information or links

Sample Email Template

HEADER From: X-ERRP-RSP <[email protected]>

To: REGISTRANTEMAILADDRESS

Subject: IMPORTANT - Domain Expiry Notification

BODY Upcoming Expiring Domains in Approximately a Month

Dear REGISTANTNAME:

As the Registrant of the domains listed below, this email is to notify you that the following domains are about to expire in approximately one month. If you wish to keep any or all of these domains, it is important that you renew your domains through your Domain Service Provider before their respective expiration dates. Please note that restoring an expired domain is more expensive, therefore please consider renewing the domains you wish to keep today.

<BEGIN OPTIONAL CONTACT DETAILS. ONLY INCLUDED IF AT LEASE ONE OF X-ERRP-URL, X-ERRP-EMAIL, OR X-ERRP-PHONE IS PROVIDED>

You can reach your Domain Service Provider here:

URL: X-ERRP-URL

EMAIL: X-ERRP-EMAIL

PHONE: X-ERRP-PHONE

<END OPTIONAL CONTACT DETAILS>

Terms and Conditions of your Domain Service Provider are available at: X-ERRP-TAC-URL

<Domain List>

Domain Name | Expiration Date

...

<BEGIN OPTIONAL FOOTER. ONLY INCLUDED IF AT LEAST X-ERRP-SIGNATURE0, X-ERRP-SIGNATURE1, X-ERRP-SIGNATURE2, OR X-ERRP-SIGNATURE3 IS PROVIDED>

X-ERRP-SIGNATURE0

X-ERRP-SIGNATURE1

X-ERRP-SIGNATURE2

X-ERRP-SIGNATURE3

<END OPTIONAL FOOTER>


For Resellers to be in compliance with the ERRP, the follow or similar wording must be in the Reseller's own terms of use with their customers.

  1. Renewal Notices. Approximately one month prior to the expiration date of a domain name, the registrant will be emailed an expiration notice to the registrant's email address. Subsequently, approximately one week prior to the expiration date of a domain name, a second notice will be emailed to the registrant's email address. And if a domain is not renewed, within five (5) days of a domain name's expiration date, the registrant will be emailed a third notice stating the domain name has expired.
  2. Renewal and Restore Fees. The fees associated with renewing gTLDs are located on the Reseller's website at URL: <<http://myresellersite.com/fees>>


  1. When start the Expired Registration Recovery Policy (ERRP) policy?
  2. How many times e-Mails will be sent out?
  3. Could I specify the sender e-Mail address per domain and account?
  4. Which part of the e-Mail can be branded?
  5. Example text of the e-Mail!
  6. Where I must show the renewal fee? (on the official homepage or customer login area are enough)
  7. Which fee I have to show if I sell domains with a bundle hosting packet?
  8. E-Mails will be still sent out if I use AUTORENEW?
  9. Do Hexonet parking my domains with own advertising if it will not renewed?
  10. Do Hexonet sold my domain if it will be in redemption or HOLD period?
  11. Which TLDs are concerned the new ERRP policy?
  12. Can I transfer domains during the HOLD period?
  13. ERRP must be a part of general terms and conditions or TLD regulations?
  14. Can I activate my domain during the HOLD period with a simple RENEW?
  15. How I could prevent the reminder e-Mails?

Retrieved from "https://wiki.hexonet.net/index.php?title=ERRP&oldid=2279"